RFR: 8159606: gc/g1/TestShrinkAuxiliaryData* tests fail because GC triggered before VM initialization completed
michail.chernov at oracle.com
Wed Jul 27 13:47:24 UTC 2016
gc/g1/TestShrinkAuxiliaryData* tests fail only with Deterministic G1 GC.
Since this is commercial feature, explanation has been sent to
confidential mail list. Short conclusion - Deterministic G1 GC policy
for young generation length differs from G1 GC policies. This fix allows
tests to be executed with Deterministic G1 GC. This change does not
affect tests execution with G1 GC.
On 07/13/2016 05:51 PM, Thomas Schatzl wrote:
> On Mon, 2016-07-11 at 17:36 +0300, Michail Chernov wrote:
>> Could I have a reviews for this small change:
>> Tests fail on some machines with different flags combinations. Tests
>> fail with message:
>> Error occurred during initialization of VM
>> GC triggered before VM initialization completed. Try increasing
>> NewSize, current value 1331K.
>> This change adds NewSize=16m and allows to avoid such failures.
> Did you investigate more about the reasons for the use of 1.4M of heap
> during startup, is this potentially because of the flight recorder
> initialization during startup?
> If so, isn't this a more generic issue then, i.e. wouldn't it be better
> to increase the minimum heap requirements if JFR is enabled during
More information about the hotspot-gc-dev