FIX: Garbage Collection Code Causes Access Violation in Long Running Java Applications (273728)

MORE INFORMATION

You encounter this problem only if applications allocate more than 16 megabytes of objects (which is measured by calling the java.lang.Runtime.totalMemory method) and "pin" two or more objects, either explicitly or implicitly. A pinned object is an object that the garbage collector cannot move in memory. To explicitly pin objects, you can use the GCNewPinnedHandle Raw Native Interface (RNI) API from native code or the com.ms.dll.DllLib.getPinnedHandle method from Java code. Primitive arrays are implicitly pinned when they are used as parameters in J/Direct or Java/COM methods.

To work around this problem, avoid explicitly pinning objects, and change calls to J/Direct and Java/COM methods that have primitive arrays as parameters to explicitly allocate arrays using the com.ms.dll.DllLib.allocHGlobal method. The allocated array would then be passed as an int parameter to the J/Direct or Java/COM method. The following code illustrates this change.

Change the following code from

/** @dll.import(???) */ 
static native void JDirectMethod (byte[] rgb);

void Test ()
{
   byte[] rgb = new byte[10];
   JDirectMethod(rgb);
}
				

to either:

/** @dll.import(???) */ 
static native void JDirectMethod (int rgb);

void Test ()
{
   int rgb = DllLib.allocHGlobal(10);

   JDirectMethod(rgb);

   DllLib.freeHGlobal(rgb);
}
				

or:

/** @dll.import(???) */ 
static native void JDirectMethod_Worker (int rgbPointer);

static void JDirectMethod (byte[] rgbObject)
{
   int cb = rgbObject.length;
   int rgbPointer = DllLib.allocHGlobal(cb);

   DllLib.copy(rgbObject, 0, rgbPointer, cb);

   JDirectMethod_Worker(rgbPointer);

   DllLib.freeHGlobal(rgbPointer);
}

void Test ()
{
   byte[] rgb = new byte[10];

   JDirectMethod(rgb);
}