JDK-8204179 : [BACKOUT] OopStorage should use GlobalCounter
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2018-05-31
- Updated: 2018-06-11
- Resolved: 2018-05-31
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 b17Fixed  |
Related Reports
|
Relates :
|
Description
Backout JDK-8202945. GlobalCounter has usage context restrictions that are incompatible with some uses of OopStorage. In particular, concurrent iteration initiated from a ConcurrentGCThread calls into the RCU-protection mechanism, and GlobalCounter doesn't allow calls from such threads.