-
Enhancement
-
Resolution: Fixed
-
P4
-
8-shenandoah, 11-shenandoah, 12, 13
-
b16
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8222619 | 12u-cpu | Aleksey Shipilev | P4 | Resolved | Fixed | master |
| JDK-8222475 | 12.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b03 |
Shenandoah resizes the heap by (un)committing the individual regions. Therefore, the true heap capacity is the "committed" size, not the maximum possible capacity. Currently, gc logs misreport the heap size, for example with -Xms1g -Xmx4g:
GC(2) Concurrent marking 183M->183M(4096M) 2.243ms
Notice "(4096M)", which is not the actual memory taken by committed heap.
GC(2) Concurrent marking 183M->183M(4096M) 2.243ms
Notice "(4096M)", which is not the actual memory taken by committed heap.
- backported by
-
JDK-8222475 Shenandoah should report "committed" as capacity
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-