JDK-8224522 : Shenandoah should apply barriers on deoptimization
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8-shenandoah,11-shenandoah,12,13
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-05-21
- Updated: 2019-05-28
- Resolved: 2019-05-22
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 13 |
|---|
13 b22Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Shenandoah, like ZGC, needs to make sure that the oops that are in deoptimized frames are passed through the barriers. Otherwise deoptimization might sneak bad oops into frames, which would then proliferate into Java heap.
Comments
|