JDK-8224793 : os::die() does not honor CreateCoredumpOnCrash option
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11,13,14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2019-05-25
  • Updated: 2020-04-03
  • Resolved: 2019-06-05
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.8-oracleFixed 13 b24Fixed 14Fixed
Related Reports
Relates :  
Description
During my investigation of the following bug:

    JDK-8188872 runtime/ErrorHandling/TimeoutInErrorHandlingTest.java fails intermittently

I determined that TimeoutInErrorHandlingTest.java was still
generating core files even though -XX:-CreateCoredumpOnCrash
was specified.

I tracked the issue down to the os::die() function.

It makes more sense to split the fix for this issue from JDK-8188872,
but they will be tested and likely pushed together.
Comments
11u Fix Request: I would like to backport this patch to 11u. This patch honors command line option 'CreateCoredumpOnCrash' to eliminate confusion. The original patch applies clean.
25-03-2020

I think os::die() is expected to always create a core dump because you should only end up there when something went badly wrong.
26-05-2019