Bug ID: JDK-8213752 Determine StringTable content liveness concurrently in G1

Type: Enhancement
Component: hotspot
Sub-Component: gc
Affected Version: 12

Priority: P4
Status: Open
Resolution: Unresolved

Submitted: 2018-11-12
Updated: 2019-03-18

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other
tbdUnresolved

Recently mechanisms for concurrent String and Symboltable cleanup have been implemented for ZGC.

These can be reused to implement the same in G1.

Relates :	JDK-8213198 - Not triggering concurrent cycle in G1 leaves string table cleanup deferred
Relates :	JDK-8219643 - Purge CLDG concurrently in G1
Relates :	JDK-8213229 - Investigate treating StringTable as weak in young collections