JDK-8064814 : Print more helpful error message when getting OOM due to low Java Heap base when running with CompressedOops
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-11-13
  • Updated: 2018-03-05
  • Resolved: 2016-07-02
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 b128Fixed
Related Reports
Relates :  
JDK-8194642 - Improve OOM error reporting for JDK8
Description
We have seen issues where users have gotten native OutOfMemory errors due to low HeapBaseMinAddress on Solaris with compressed refs. This is hard to know for most users. We should improve the error message on native OOM to help here.

Best case, we would know when this happens, and only print something if this is the issue.

If that is not possible, we could always print this when running on Solaris with compressed references.
Comments
FC Extension Request : Please approve this small enhancement for jdk9. This diagnostic enhancement improves the error message reported when a Java application running with 64-bit JVM runs out of native heap space. The problem is explained here: https://blogs.oracle.com/poonam/entry/running_on_a_64bit_platform The fix is ready and reviewed: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2016-May/019360.html
10-06-2016