JDK-8048085 : Aborting marking just before remark results in useless additional clearing of the next mark bitmap
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8u40,9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-06-25
- Updated: 2015-01-21
- Resolved: 2014-07-21
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 |
|---|---|
8u40Fixed  |
9 b26Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
If before a full GC (that is already in the vm operation queue) a GC Remark happens, the VM continues to clear the next bitmap although it has already been cleared when aborting it. This is additional, needless work. Guard the call to _cm->clearNextBitmap() in ConcurrentMarkThread::run() with the appropriate condition.
Comments
|