-
Enhancement
-
Resolution: Fixed
-
P4
-
8-shenandoah, 11-shenandoah, 12, 13
-
b04
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8218667 | 12.0.2 | Roman Kennke | P4 | Resolved | Fixed | b01 |
In Shenandoah, we currently start cleanup phase when we dive into concurrent evacuation (and only then), and after the cycle (unconditionally). However, we only create trashed regions in final-mark (immediate garbage and/or garbage from previous cycle), and might skip evacuation altogether, and may not actually create trash at end of cycle if we merge update-refs onto subsequent concurrent-mark. Let's start cleanups where we actually need them: once unconditionally before conc-evac and once after final-update-refs.
- backported by
-
JDK-8218667 Shenandoah: Kick up cleanup phases in the right places
- Resolved