JDK-8042557 : compiler/uncommontrap/TestSpecTrapClassUnloading.java fails with: GC triggered before VM initialization completed
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: emb-8u26,9
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2014-05-06
  • Updated: 2014-08-14
  • Resolved: 2014-05-26
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b17Fixed
Related Reports
Blocks :  
Description
----------System.out:(4/265)----------
CompilerOracle: exclude java/lang/reflect/Method.invoke
CompilerOracle: exclude sun/reflect/DelegatingMethodAccessorImpl.invoke
Error occurred during initialization of VM
GC triggered before VM initialization completed. Try increasing NewSize, current value 1536K.

The test specifies -Xmx:

command: main -XX:+IgnoreUnrecognizedVMOptions -XX:-TieredCompilation -XX:-UseOnStackReplacement -XX:-BackgroundCompilation -XX:+UseTypeSpeculation -XX:TypeProfileLevel=222 -XX:CompileCommand=exclude,java.lang.reflect.Method::invoke -XX:CompileCommand=exclude,sun.reflect.DelegatingMethodAccessorImpl::invoke -Xmx1M TestSpecTrapClassUnloading

Comments
ILW=Test fail due to small Xmx, unclear if neccessary; every now and then, none=LMH=P5
14-05-2014

This is not a duplicate of JDK-8040935. This tests fails because it specifies a really small heap sizes and as an effect of that a GC is triggered during initialization. What is the reason for using such a small Xmx-value? Can the test be updated to not specify Xmx?
14-05-2014

Please try to avoid specifying -Xmx by any means!
06-05-2014