Hi Everyone,
I'm working on the bug https://bugs.openjdk.java.net/browse/JDK-7067973.
It is a test bug as the test doesn't guarantee memory allocated from the
Old Gen, if the used memory is zero and doesn't cross the threshold, no
notification is sent, so both the main thread and Checker thread are
blocked to wait for the GC notification.
so the suggested fix is similar as the fix ResetPeakMemoryUsage.java
<http://hg.openjdk.java.net/jdk8/tl/jdk/rev/a0896634ab46> to create big
object to make sure the old gen usage crosses the threshold and run test
with different GC vmoptions. The different GC vmoptions are planed to be
tested as below:
@run main/othervm/timeout=300 -XX:+PrintGCDetails -XX:+UseSerialGC
CollectionUsageThreshold
@run main/othervm/timeout=300 -XX:+PrintGCDetails -XX:+UseParallelGC
CollectionUsageThreshold
@run main/othervm/timeout=300 -XX:+PrintGCDetails -XX:+UseG1GC
CollectionUsageThreshold
@run main/othervm/timeout=300 -XX:+PrintGCDetails
-XX:+UseConcMarkSweepGC CollectionUsageThreshold
@run main/othervm/timeout=300 -XX:+PrintGCDetails -Xmx2m
-XX:+UseConcMarkSweepGC -XX:+ExplicitGCInvokesConcurrent
CollectionUsageThreshold
@run main/othervm/timeout=300 -XX:+PrintGCDetails -Xmx2m -Xconc
-XX:+ExplicitGCInvokesConcurrent CollectionUsageThreshold
@run main/othervm/timeout=300 -XX:+PrintGCDetails -Xmx2m -XX:+UseG1GC
-XX:+ExplicitGCInvokesConcurrent CollectionUsageThreshold
Can you please give some suggestion about the solution?
BTW, the fix is still in an internal discussion, i'll post the webrev
when it is ready.
Thanks,
Eric
