JDK-8202945 : OopStorage should use GlobalCounter
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2018-05-10
- Updated: 2018-06-21
- Resolved: 2018-05-29
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.
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 |
|---|
11 b16Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
OopStorage introduced a bespoke RCU-inspired mechanism in the management of its arrays of blocks (part of JDK-8200557). This mechanism was developed before GlobalCounter (JDK-8195099) was available, and has continued to be used due to a limitation of GlobalCounter (it could attempt to safepoint, due to JDK-8191798). Now that the limitation has been addressed, OopStorage should use GlobalCounter and discard its private mechanism.