-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b06
-
generic
-
generic
With the recent reimplementation of the StringTable using ConcurrentHashtable and OopStorage, treating it as a strong root rather than a weak root in young collections may no longer provide best performance.
- blocks
-
JDK-8217578 Shenandoah cleanup unused timings after concurrent string table change
-
- Resolved
-
- relates to
-
JDK-8217778 StringTable cleanup miscalculates amount of dead objects
-
- Resolved
-
-
JDK-8310176 JDK 11 G1 crash during full GC with +UseStringDeduplication
-
- Resolved
-
-
JDK-8213752 Determine StringTable content liveness concurrently in G1
-
- Open
-
-
JDK-8221558 Remove obsolete uses of OopStorage::ParState<false, false> _par_state
-
- Resolved
-
-
JDK-8037956 Merge String Deduplication work with String/Symbol table work
-
- Closed
-
-
JDK-8217522 Missing barriers in some java_lang_String assertion code after JDK-8217442
-
- Closed
-
-
JDK-8213198 Not triggering concurrent cycle in G1 leaves string table cleanup deferred
-
- Open
-
-
JDK-8215709 WeakProcessor should also report task item information
-
- Open
-