JDK-8222492 : G1 unnecessarily scans remembered set cards for regions that already have been evacuated
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 12,13
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2019-04-15
- Updated: 2019-08-08
- Resolved: 2019-05-18
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
|
Duplicate :
|
|
|
Relates :
|
Description
When evacuating optional regions G1 iterates over the remembered sets of these regions. These remembered sets may contain cards in other, in previous iterations evacuated optional regions. Since we do not update the scan_top() filter used for filtering out such cards between iterations, such cards are not filtered out and the corresponding heap scanned. This is a day-one minor performance issue for AMGC, and causes crashes since implementation of JDK-8218668.
Comments
|