JDK-8165808 : Add release barriers when allocating objects with concurrent collection
- Type: Sub-task
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-09-10
- Updated: 2021-06-27
- Resolved: 2016-09-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.
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 8 | JDK 9 | Other |
|---|---|---|
| 8u301Fixed | 9 b139Fixed  |
openjdk8u282Fixed |
Description
When allocating an object and the associated memory -> object transition might be visible to a concurrent collector, use a release barrier when setting the klass to ensure other low level object initializations are complete.
Comments
|