JDK-8281460 : Let ObjectMonitor have its own NMT category
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 19
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-02-08
  • Updated: 2022-02-25
  • Resolved: 2022-02-11
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 19
17.0.3Fixed 19 b10Fixed
Related Reports
Blocks :  
JDK-8281450 - Remove unnecessary operator new and delete from ObjectMonitor
Relates :  
JDK-8281450 - Remove unnecessary operator new and delete from ObjectMonitor
Description
It would be useful to distinguish ObjectMonitor allocations in NMT, as a simple way to both to see the needed footprint as well as the number of allocated monitors.

Note, this needs JDK-8281450 as a prerequisite.
Comments
Fix Request jdk17u: Clean backport, very small fix, very low risk. I'd like to backport this to make it more obvious if a VM uses a lot of memory for Object Monitors. Before this patch, this number was hidden in mtInternal.
23-02-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk17u-dev/pull/166 Date: 2022-02-16 09:37:02 +0000
16-02-2022
Changeset: a037b3c3 Author: Thomas Stuefe <stuefe@openjdk.org> Date: 2022-02-11 07:21:04 +0000 URL: https://git.openjdk.java.net/jdk/commit/a037b3c35831f029d23a88bdd49e7f2c2d951631
11-02-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/7378 Date: 2022-02-08 08:10:05 +0000
08-02-2022