JDK-8256306 : ObjectMonitor::_contentions field should not be 'jint'
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2020-11-12
  • Updated: 2021-07-01
  • Resolved: 2021-06-23
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 18
18 b04Fixed
Related Reports
Relates :  
JDK-8253064 - monitor list simplifications and getting rid of TSM
Description
[~coleenp] mentioned this RFE during the JDK-8253064 review: 

 src/hotspot/share/runtime/objectMonitor.hpp
@@ -179,7 +171,7 @@ class ObjectMonitor {
  jint  _contentions;               // Number of active contentions in enter(). It is used by is_busy()

Future RFE - can we replace jint with int32_t or even int or some C++ types. We're trying not to have Java types leak into runtime code since this doesn't directly interface with Java.
Comments
Changeset: f3ba2690 Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2021-06-23 14:27:31 +0000 URL: https://git.openjdk.java.net/jdk/commit/f3ba2690c5b34673ebf6836c87e45477e1ff91c3
23-06-2021
The _waiter's field is also a jint and should also be changed with this CR.
21-05-2021
[~coleenp] - feel free to update the RFE's description as needed.
12-11-2020