Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 13
Affects Version/s: None
Component/s: hotspot
Labels:
- gc-pending-review

Subcomponent:
gc
Resolved In Build:
b06
CPU:

generic
OS:

generic

Current STW collectors presently treat the StringTable as a strong root in young collections. This avoids the need to walk the StringTable and delete dead entries in a young collection. Instead it walks the StringTable and marks all the strings, as one of the in-parallel root marking phases.

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

(4 relates to)

Assignee:: Thomas Schatzl
Reporter:: Kim Barrett
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: 2018-10-31 17:24
Updated:: 2023-06-15 18:33
Resolved:: 2019-01-29 02:33

Details

Description

Attachments

Issue Links

Activity

People

Dates