Request for review: 8006628: NEED_TEST for JDK-8002870
john.cuthbertson at oracle.com
Mon Jan 28 18:58:54 UTC 2013
In addition to what Jon suggests (i.e. using System.gc() to guarantee a
GC), please add -XX:+ExplicitGCInvokesConcurrent. The addition of this
flag will cause G1 to perform an incremental GC (instead of the full GC
that a System.gc() call provokes). IIRC the PLAB resizing code is only
exercised at the end of an incremental GC.
On 1/28/2013 9:18 AM, Jon Masamitsu wrote:
> Can this test be implemented using a call to
> System.gc() instead of trying to fill up the heap
> to provoke a GC?
> On 01/21/13 03:14, Filipp Zhinkin wrote:
>> Hi all,
>> Would someone review the following regression test please?
>> Test verifies that VM will not crash with G1 GC and ParallelGCThreads
>> == 0.
>> To ensure that it is true test allocates array until OOME.
>> Max heap size is limited by 32M for this test to ensure that GC will
>> Since crash could occur only during PLAB resizing after GC,
>> ResizePLAB option is explicitly turned on.
More information about the hotspot-gc-dev