JDK-8013934 : Garbage collection event for CMS has wrong cause for System.gc()
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs24,hs25
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-05-06
- Updated: 2013-06-26
- Resolved: 2013-05-20
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 7 | Other |
|---|---|
7u40Fixed  |
hs24Fixed |
Description
The vm/gc/collector/garbage_collection event has the wrong cause when System.gc() is used to trigger a concurrent CMS collection (by setting -XX:+ExplicitGCInvokesConcurrent). The expected cause is "System.gc()" but "CMS Concurrent Mark" is reported.
Comments
|