JDK-8054368 : nsk/jdi/VirtualMachine/exit/exit002 crash with detail tracking on (NMT2)
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris
  • CPU: x86
  • Submitted: 2014-08-05
  • Updated: 2015-01-21
  • Resolved: 2014-08-14
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.
8u40Fixed 9 b29Fixed
This is a racing issue during debuggee exit.

The debuggee calls ::exit() to force the process to exit, by-passes VM shutdown sequence. As the result, C runtime starts to destroy static variables while VM is still using them.

This particular case, it is VirtualMemoryTracker::_reserved_regions.
ILW MLM = P4 I: Medium, Crashes when debugee calls forceExit() L: Low, Only triggered by debugee doing forceExit() and only seen on Solaris so far W: Medium, Don't run with NMT on when debugging