Bug ID: JDK-8206423 Use locking for cleaning ResolvedMethodTable

JDK-8206423 : Use locking for cleaning ResolvedMethodTable

Type: Enhancement
Component: hotspot
Sub-Component: runtime
Affected Version: 11

Priority: P3
Status: Resolved
Resolution: Fixed

Submitted: 2018-07-05
Updated: 2019-05-28
Resolved: 2018-08-21

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.

JDK 12
12 b08Fixed

Related Reports

Relates :	JDK-8195097 - Make it possible to process StringTable outside safepoint
Relates :	JDK-8206424 - Use locking for cleaning ProtectionDomainTable
Relates :	JDK-8213307 - G1 should clean up RMT with ClassUnloadingWithConcurrentMark
Relates :	JDK-8195100 - Use a low latency hashtable for SymbolTable

Description

The ResolvedMethodTable is cleaned during class unloading but could be cleaned concurrently if it uses the ConcurrentHashTable instead.

Comments

Or use ResolvedMethodTable_lock around inserts and cleanup, and measure performance. That would be simpler.

18-07-2018