JDK-8320320 : Make ObjectMonitor owner field the ThreadID
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2023-11-17
  • Updated: 2024-01-24
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
Related Reports
Relates :  
JDK-8320317 - ObjectMonitor NotRunnable is not really an optimization
Relates :  
JDK-8320323 - ObjectWaiter queue for ObjectMonitors don't support virtual threads
Description
Using the ThreadID as the owner for the ObjectMonitor makes it unambiguous for Loom, as the ThreadID is unique and the JavaThread can have different virtual threads mounted on it (ie so is not useful).
Comments
Draft PR: https://github.com/openjdk/jdk/pull/16441
17-11-2023