-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 8-shenandoah, 11, 16, 17
-
Component/s: hotspot
-
b19
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8267323 | 16u-cpu | Zhengyu Gu | P3 | Resolved | Fixed | master |
| JDK-8267058 | 16.0.2 | Zhengyu Gu | P3 | Resolved | Fixed | b05 |
| JDK-8266917 | 11.0.12 | Zhengyu Gu | P3 | Resolved | Fixed | b02 |
Shenandoah uses MaxHeapSize to calculate region size, then aligns up heap size to region size alignment, but when it calculates region count, it does not take alignment into account, that may result 1 region short than actual count.
MaxHeapSize eventually aligns to to HeapAlignment (which is region size in Shenandoah case), but it is too late.
MaxHeapSize eventually aligns to to HeapAlignment (which is region size in Shenandoah case), but it is too late.
- backported by
-
JDK-8266917 Shenandoah: Shenandoah heap region count could be off by 1
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk16u/319621c3
-
Commit
openjdk/jdk/ff5bb8cf
-
Review
openjdk/jdk16u/110
-
Review
openjdk/jdk/3504
(3 links to)