-
Task
-
Resolution: Fixed
-
P4
-
repo-shenandoah
-
b06
Shenandoah typically takes 4 safepoints per GC cycle. Although Shenandoah itself does not spend much time on these safepoints, it may still take quite some time for all of the mutator threads to reach the safepoint. The occasionally long time-to-safepoint increases latency in the higher percentiles. It may not be possible to eliminate all of these safepoints, but the `init-update-refs` safepoint should be the easiest to eliminate.
- causes
-
JDK-8348092 Shenandoah: assert(nk >= _lowest_valid_narrow_klass_id && nk <= _highest_valid_narrow_klass_id) failed: narrowKlass ID out of range (3131947710)
-
- Resolved
-
- relates to
-
JDK-8350898 Shenandoah: Eliminate final roots safepoint
-
- Open
-
-
JDK-8348268 Test gc/shenandoah/TestResizeTLAB.java#compact: fatal error: Before Updating References: Thread C2 CompilerThread1: expected gc-state 9, actual 21
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/764d70b7
-
Review(master) openjdk/jdk/22688