On 10/23/2013 7:32 AM, Jaroslav Bachorik wrote:
I've updated the patch. The GC is called even before the first attempt
to get the pool memory usage and System.gc() is used to perform GC (no
MXBean checks). This should simplify the change a bit.
http://cr.openjdk.java.net/~jbachorik/8020467/webrev.02
This change is okay. It will force GC once per each memory pool that
supports usage threshold (I think 3 memory pools) which is not a huge
issue. Perhaps a more reliable option is to make it an othervm test and
allocating large object and calling GC once before the verification.
Mandy
