Maintenance Notice

The site will be undergoing maintenance on 15th Dec 2017 21:00 PST to 16th Dec 2017 1:00 AM PST.
JDK-7154333 : JVM fails to start if -XX:+AggressiveHeap is set
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 7u4
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-03-15
  • Updated: 2013-07-18
  • Resolved: 2012-03-24
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 Availabitlity Release.

To download the current JDK release, click here.
JDK 7 JDK 8 Other
7u4Fixed 8Fixed hs23Fixed
Starting in b05, we can no longer run with -XX:+AggressiveHeap:

/net/koori/onestop/jdk/7u4/promoted/all/b05/binaries/solaris-x64/bin/java -d64 -XX:+AggressiveHeap -version Error occurred during initialization of VM
Incompatible compilation policy selected

This is still broken in b15.




EVALUATION AggressiveHeap sets the compilation policy for some reason, and the policy choice conflict with tiered. I don't think it should be setting the policy at all.