Maintenance Notice

The bugs.java.com 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
Description
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.

Comments
EVALUATION http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/56ee89841dc4
2012-03-28

EVALUATION http://hg.openjdk.java.net/hsx/hsx23/hotspot/rev/ab565ffd9ec9
2012-03-22

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-comp/hotspot/rev/56ee89841dc4
2012-03-16

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.
2012-03-15