JDK-8225716 : G1 GC: Undefined behaviour in G1BlockOffsetTablePart::block_at_or_preceding
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8u212,11.0.3
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2019-06-13
- Updated: 2020-06-09
- Resolved: 2019-06-19
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 | JDK 13 | JDK 14 | JDK 8 | Other |
|---|---|---|---|---|
| 11.0.4Fixed | 13 b26Fixed  |
14Fixed |
8u261Fixed |
openjdk8u222Fixed |
Related Reports
|
Relates :
|
Description
The Block Offset Table is accessed racily in many places. This is UB, but I suspect the authors of G1 assumed that the UB was "benign". In fact it is not, and there is a narrow race condition which causes G1 to crash at times of heavy stress. The bug has only ever been observed on 86-32, but it isn't a target-specific bug. It's probably not specific to G1 either.
Comments
|