-
Bug
-
Resolution: Fixed
-
P3
-
18
-
b13
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8327366 | 17.0.12 | Goetz Lindenmaier | P3 | Resolved | Fixed | b01 |
In JDK-8269914 the heap region usage was factored into G1HeapPrinterMark. The region information is printed in the destructor and for the Full GC this is a bit to late. We have:
```
G1FullCollector collector(this, explicit_gc, do_clear_all_soft_refs, do_maximum_compaction);
GCTraceTime(Info, gc) tm("Pause Full", NULL, gc_cause(), true);
```
And G1FullCollector has a member G1FullGCScope which in turn has a G1HeapPrinterMark as a member. The order can be easily changed by first starting the timer and then create the collector object.
```
G1FullCollector collector(this, explicit_gc, do_clear_all_soft_refs, do_maximum_compaction);
GCTraceTime(Info, gc) tm("Pause Full", NULL, gc_cause(), true);
```
And G1FullCollector has a member G1FullGCScope which in turn has a G1HeapPrinterMark as a member. The order can be easily changed by first starting the timer and then create the collector object.
- backported by
-
JDK-8327366 G1 heap region info print order changed by JDK-8269914
-
- Resolved
-
- relates to
-
JDK-8269914 Factor out heap printing for G1 young and full gc
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/158f91a8
-
Commit
openjdk/jdk/f11e099a
-
Review
openjdk/jdk17u-dev/2261
-
Review
openjdk/jdk/5252
(1 links to)