-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
17, 21, 25, 26
While working on related bug, I found that Shenandoah commit/uncommit code has a few issues:
1. It throws Java OOME on commit/uncommit failures. These should actually be VM-level out of memory errors, so they are properly fatal.
2. Throwing OOME on uncommit looks fairly weird.
3. We are not zapping on the newly committed regions.
1. It throws Java OOME on commit/uncommit failures. These should actually be VM-level out of memory errors, so they are properly fatal.
2. Throwing OOME on uncommit looks fairly weird.
3. We are not zapping on the newly committed regions.
- links to
-
Review(master) openjdk/jdk/26502