JDK-8158033 : Notify_tracing() misplaced for intended purpose
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-05-27
  • Updated: 2016-07-07
  • Resolved: 2016-06-13
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 b126Fixed
Related Reports
Relates :  
JDK-8159700 - bigapps/Kitchensink/modulePostprocess fails in nightly run
Description
The intent when putting in the notify_tracing() hook into debug.cpp (report_java_out_of_memory()) was to intercept a state believed to be a VM termination state, especially when OOME is thrown. Since it is totally valid that Java code catches OOME, and this location actually goes back to Java, this is the wrong location for this hook.

In addition, the hook should not be typed for OOME only, but generic for any exit condition (normal / OOME / crash).

This should instead have been put into java.cpp (before_exit()) and in VMError.cpp (report_vm_die()).