JDK-8036673 : G1: Abort weak reference processing if mark stack overflows
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8u20,9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-03-05
- Updated: 2014-07-29
- Resolved: 2014-03-17
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 |
|---|---|
8u20Fixed  |
9 b08Fixed |
Related Reports
|
Blocks :
|
|
|
Duplicate :
|
Description
In ConcurrentMark::weakRefsWork(), if the mark stack overflows we should not proceed to prune the string and symbol tables because we can't trust the g1_is_alive closure until marking has completed. Before starting to unlink elements from the string and symbol table we should check that has_overflown() is false.