P2
Tests could fail with
"Error occurred during initialization of VM
GC triggered before VM initialization completed. Try increasing NewSize, current value 1331K."
when running in AOT mode using different GC in training and production runs.
The issue is seen at least when ZGC was used in training run and G1 GC was used in production run.
As found below by [~eosterlund], this is because of G1's policy to preemptively start concurrent marking during humongous object allocation. The VM may not be ready to perform a GC this time. Simply do not issue the GC at that time.
Most likely related toJDK-8371986 where the default value of InitialRAMPercentage has been removed/set to 0.
"Error occurred during initialization of VM
GC triggered before VM initialization completed. Try increasing NewSize, current value 1331K."
when running in AOT mode using different GC in training and production runs.
The issue is seen at least when ZGC was used in training run and G1 GC was used in production run.
As found below by [~eosterlund], this is because of G1's policy to preemptively start concurrent marking during humongous object allocation. The VM may not be ready to perform a GC this time. Simply do not issue the GC at that time.
Most likely related to
- caused by
-
JDK-8373023 [REDO] Remove the default value of InitialRAMPercentage
-
- Resolved
-
- duplicates
-
JDK-8374803 G1 tries to start a concurrent mark allocating a humongous object during initialization
-
- Closed
-
- links to
-
Review(master)
openjdk/jdk/29119