Bug ID: JDK-6786879 Race in jvmti GetObjectMonitorUsage could lead to crashes

Type: Bug
Component: hotspot
Sub-Component: jvmti
Affected Version: hs14

Priority: P3
Status: Closed
Resolution: Cannot Reproduce
OS: generic
CPU: generic

Submitted: 2008-12-18
Updated: 2023-12-13
Resolved: 2016-11-30

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
tbdResolved

Race in jvmti GetObjectMonitorUsage could lead to crashes.
See more info in comments.

According to bug report, this can only be reproduced on IA64, which is no longer a supported platform. Closing as CNR.

30-11-2016

This issue must be reproduced first with a newly developed test before Dev can actively work on the fix.

07-08-2013

Relates :	JDK-8007476 - assert(the_owner != NULL) failed: Did not find owning Java thread for lock word address
Relates :	JDK-7154963 - crash in JvmtiEnvBase::get_current_contended_monitor()