- 
    Enhancement 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    8-shenandoah, 11-shenandoah, 12, 13
- 
        b21
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8228949 | 12u-cpu | Aleksey Shipilev | P4 | Resolved | Fixed | master | 
| JDK-8223959 | 12.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b03 | 
                    Shenandoah heap regions checks verify that initial heap size covers at least 10 regions. This means the lowest uncommitted size is at least 10*RegionSize, which is a lot for large heaps. This seems to be the reminiscent of old resizing scheme, where Shenandoah could have run with "initial heap" for a long time, before GC code decided to resize. There is little sense it in now: Shenandoah would commit regions up to max_capacity if needed, including during the initial barrage of allocations. We should instead check that "max" heap size covers at least 10 regions.
            
- backported by
- 
                    JDK-8223959 Shenandoah should allow arbitrarily low initial heap size -           
- Resolved
 
-         
- 
                    JDK-8228949 Shenandoah should allow arbitrarily low initial heap size -           
- Resolved
 
-