JDK-8227031 : Print NMT statistics on fatal errors
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-07-01
  • Updated: 2021-06-30
  • Resolved: 2019-07-11
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 11 JDK 13 JDK 14
11.0.6Fixed 13.0.4Fixed 14 b06Fixed
Related Reports
Relates :  
JDK-8227072 - NMT detailed report should work in native OOM situations.
Relates :  
JDK-8261297 - NMT: Final report should use scale 1
Relates :  
JDK-8227254 - Optionally preallocate buffer to make error handling more stable on native OOM
Description
We have PrintNMTStatistics, a very useful switch which will cause the VM to print out the NMT statistics if the VM exits normally.

Currently it does not work if the VM exits due to a fatal error. But especially in fatal exits due to native OOM a NMT report would be very helpful.


Note that we already print an abridged NMT report into the hs-err file, but this is not what this item is about. This RFE is about printing summary or detailed NMT info to stdout, like it would happen for a normal VM exit with "-XX:+PrintNMTStatistics" enabled.
Comments
Fix request (13u): The change applies cleanly, tested with tier1.
15-05-2020
Fix Request: I'd like to downport this patch to 11. It improves the usability of NMT in OOM situations. The patch is quite harmless. It applies cleanly. All SAP nightlies went fine.
23-09-2019
URL: https://hg.openjdk.java.net/jdk/jdk/rev/2d1acda7555a User: stuefe Date: 2019-07-11 04:51:39 +0000
11-07-2019