JDK-8216982 : Assertion poison page established too early
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-01-14
  • Updated: 2024-12-05
  • Resolved: 2019-01-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 11 JDK 13
11.0.3Fixed 13 b04Fixed
Related Reports
Relates :  
JDK-8191101 - Show register content in hs-err file on assert
Relates :  
JDK-8227275 - Within native OOM error handling, assertions may hang the process
Description
8191101 "Show register content in hs-err file on assert" added a mechanism to show registers when an assert happens, using a one-shot poison page mechanism.

This poison page is established using os::reserve_memory and friends. However, this happens at a point where os:: subsystem initialization did not run completely through. This causes errors for features used by the os:: subsystem which did not have a chance to be initialized yet, eg the NUMA aware allocation.
Comments
Fix Request: Bug clashes with NUMA initialization. The fix is to move the initialization of the assertion poison page down after os::init_2. The risk is minimal.
15-01-2019
URL: http://hg.openjdk.java.net/jdk/jdk/rev/0b2574a2a6c7 User: stuefe Date: 2019-01-15 07:06:22 +0000
15-01-2019