JDK-8163437 : Initialization logic error in PerfMemory
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2016-08-09
  • Updated: 2018-01-03
  • Resolved: 2018-01-03
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
11Resolved
Related Reports
Duplicate :  
JDK-8151815 - Could not parse core image with JSnap.
Relates :  
JDK-8158854 - Ensure release_store is paired with load_acquire in lock-free code
Description
./share/vm/runtime/perfMemory.cpp: OrderAccess::release_store(&_initialized, 1);

Incorrect usage: the initialization logic is broken. We write _initialized last with release_store but there is no load_acquire to match with it. Worse the only code that checks _initialized is PerfMemory:;destroy. The actual PerfMemory functions either don't check initialization or use an assert that checks a different field!
Comments
All of the issues raised here were addressed by the fix for JDK-8151815. But the final review for that: http://mail.openjdk.java.net/pipermail/serviceability-dev/2017-October/021958.html still exposed issues with this code during an abort.
03-01-2018