JDK-8275800 : Redefinition leaks MethodData::_extra_data_lock
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 18
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-10-22
  • Updated: 2022-01-03
  • Resolved: 2021-10-27
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 17 JDK 18
17.0.3-oracleFixed 18 b21Fixed
Related Reports
Relates :  
JDK-8274794 - Print all owned locks in hs_err file
Relates :  
JDK-8232112 - MDO extra_data_lock leaks during class unloading
Description
When we deallocate metadata for redefinition, we don't call the Mutex destructor, which leaks the PlatformMutex and the name.
And broke JDK-8274794.
Comments
Fix request [17u] I backport this for parity with 17.0.3-oracle. The change is not trivial, but we should take a fix for a leak. Clean backport. SAP nightly testing passes.
31-12-2021
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk17u-dev/pull/49 Date: 2021-12-30 12:18:36 +0000
30-12-2021
Changeset: 40606021 Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2021-10-27 12:09:46 +0000 URL: https://git.openjdk.java.net/jdk/commit/40606021ee6b7d18674e36b3f6249f1ca8a7647e
27-10-2021