Shenandoah: Improve commit/uncommit handling

XMLWordPrintable

    • gc
    • b10

      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.
       

            Assignee:
            Aleksey Shipilev
            Reporter:
            Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: