-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 24
-
Component/s: hotspot
-
b27
The changes in JDK-8297692 broke code root scan timing - the measurement scope for the G1EvacPhaseWithTrimTimeTracker scope extends beyond reading the changed values from it.
So code root scan times end up in "Other" time
So code root scan times end up in "Other" time
- caused by
-
JDK-8297692 Avoid sending per-region GCPhaseParallel JFR events in G1ScanCollectionSetRegionClosure
-
- Resolved
-
- relates to
-
JDK-8358342 G1: G1CodeRootSet performance breaks down on even moderate load
-
- Open
-
- links to
-
Commit(master)
openjdk/jdk/160148cc
-
Review(master)
openjdk/jdk/28513