JDK-8263387 : G1GarbageCollection JFR event gets gc phase, not gc type
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-03-10
- Updated: 2021-03-22
- Resolved: 2021-03-15
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 17 |
|---|
17 b14Fixed  |
Related Reports
|
Relates :
|
Description
The enum attached to G1YCType is supposed to be the "type" of young gc (there is no further description for it). Currently this is mapped to GC "phases" (normal collections, during mark or rebuild, mixed collections, ...) which is very likely not the intention to show in the JFR event. It looks like that G1YCType is only used for JFR. I think the enum can be removed and G1CollectorPolicy::PauseKind used. From an end-user POV this is not an issue as the values that are printed look like pause names, but internally extra "phases" do not make sense. Hence I'm tagging this as enhancement/cleanup. (or the equivalent enums from JDK-8143041)
Comments
|