Carsten Varming 3a33f5eb9d Fix JDK9 direct ByteBuffer cleaner invocation and initialize Cleaner0 when PlatformDependent0 is initialized. ... Motivation: The clean method in java.base/jdk.internal.ref.Cleaner is not accessible to methods outside java.base. This prevents Cleaner0.freeDirectBuffer from actually calling the clean method on JDK9. The issue could have been caught earlier if Cleaner0 is initialized when PlatformDependent0 is initialized and logging statements in the static initializer in Cleaner0 would be close to the logging statements in the static initializer in PlatformDependent0. Modifications: Try casting the cleaner obtained from a ByteBuffer to Runnable and use Runnable.run if possible. All Cleaners in JDK9 implements Runnable. Fall back to the clean method if the cleaner does not implement Runnable. The fallback preserves the behavior on JDK8 and earlier. Try to free the direct ByteBuffer allocated during static initialization of PlatformDependent0. This cause Cleaner0 to be initialized when PlatformDependent0 is initialized, and logging statements from the static initializers will be close together. Result: Cleaner0.freeDirectBuffer works as intended on JDK9 and logging shows that Cleaner0.freeDirectBuffer works as intended.		2016-07-14 22:24:02 +02:00
..
src	Fix JDK9 direct ByteBuffer cleaner invocation and initialize Cleaner0 when PlatformDependent0 is initialized.	2016-07-14 22:24:02 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2016-07-01 10:33:32 +02:00