JDK-6694099 : Hotspot vm_exit_out_of_memory should dump core
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs12
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-04-25
  • Updated: 2017-05-16
  • Resolved: 2008-07-15
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 6 JDK 7 Other
6u14Fixed 7Fixed hs14Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
The purpose of this RFE is to improve the ability to debug situations where the VM exits unexpectedly via one of the vm_abort/vm_exit code paths.  In some cases we don't dump core where arguably we should.

1. By default, dump core for any abort/C Heap OOM *except* "simple" failures during startup (vm_exit_during_initialization).
2. Revisit jni_FatalError: os::abort(false) (see comments).
3. Consider VM options to change the default behaviors (may not be needed.)
4. Ensure dumping core implies creating hs_err log as well (this may already be true in all cases.)

EVALUATION The fix will enable dumping of core in product mode as well when VM runs out of C-heap.