JDK-6395139 : GC time stamps should be relative to the start of the JVM
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 6
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2006-03-07
- Updated: 2012-10-13
- Resolved: 2006-03-25
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.
| Other | JDK 6 |
|---|---|
| 1.4.2_13Fixed | 6 b77Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The GC time stamps when printed with -XX:+PrintGCTimeStamps consider time 0 the first logged GC event. This prevents customers from being able to compare time stamps in their application with GC time stamps. The fix should be straightforward; basically, to make sure that time 0 is the start of the JVM.
Comments
|