JDK-6963209 : G1: remove the concept of abandoned pauses
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs19
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-06-22
- Updated: 2013-09-18
- Resolved: 2011-04-23
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 6 | JDK 7 | Other |
|---|---|---|
| 6u21pFixed | 7Fixed  |
hs19Fixed |
Related Reports
|
Relates :
|
Description
Abandoned pauses in G1 are ones for which we end up having an empty collection set. So, we deem there's no point in actually doing the pause and we bail out early. As part of "6944166: G1: explicit GCs are not always handled correctly" we are disabling abandoned pauses, i.e., we assume a pause is never abandoned even if the collection set is empty (see that CR for the reasons for this). As part of this CR we'll remove the code paths that are associated with abandoned pauses. This work is done separately to avoid adding more changes to 6944166 and keep the code reviews somewhat more managable.
Comments
|