JDK-8232232 : G1RemSetSummary::_rs_threads_vtimes is not initialized to zero
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-10-15
- Updated: 2019-10-21
- Resolved: 2019-10-16
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 14 |
|---|
14 b19Fixed  |
Related Reports
|
Relates :
|
Description
G1RemSetSummary::_rs_threads_vtimes is not initialized to zero in the constructor "G1RemSetSummary(G1RemSet* rem_set)", this leads to invalid values in GC logs for "Concurrent refinement threads times (s)". Reproducible with: $ java -XX:+UnlockDiagnosticVMOptions -XX:G1SummarizeRSetStatsPeriod=1 -Xlog:gc+remset*=trace -XX:ParallelGCThreads=8 -version (It is more obvious in a fastdebug build.) In addition, after JDK-8231153, the field G1RemSetSummary::_rem_set is never used. Removing this field and merging the two constructors of G1RemSetSummary will fix the bug and clean up the code.
Comments
|