JDK-8194642 : Improve OOM error reporting for JDK8
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2018-01-04
  • Updated: 2019-01-14
  • Resolved: 2018-03-23
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 8
8u192 b01Fixed
Related Reports
Relates :  
JDK-8026333 - hs_err improvement: Print GC Strategy
Relates :  
JDK-8026324 - hs_err improvement: Add summary section to hs_err file
Relates :  
JDK-8064814 - Print more helpful error message when getting OOM due to low Java Heap base when running with CompressedOops
Relates :  
JDK-8026336 - hs_err improvement: Print compilation mode, server, client or tiered
Description
Compared to JDK9, JDK8u version of the error reporting has too little information on OOM related problems.
This enhancement is to improve the error reporting to handle possible reasons for OOM.
Such as 
1. UseCompressedOops
2. 32 bit 
3. Possible suggestions for 64 bit (Already exist with more specific cases)

The above suggested code changes are already present in 9 as part of "JDK-8136421: JEP 243: Java-Level JVM Compiler Interface"
We could backport related changes in 8u.
Comments
There are couple of improvements in src/hotspot/share/utilities/vmError.cpp done in jdk9, need to consider them for 8.
25-01-2018