JDK-8301749 : Tracking malloc pooled memory size
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 21
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-02-03
  • Updated: 2024-07-15
  • Resolved: 2023-02-20
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 21
21 b11Fixed
Related Reports
CSR :  
Relates :  
Relates :  
Description
Memory not allocated via NMT and uncommitted memory contributes to a discrepancy between NMT and RSS.
It can be hard to distinguish between these cases.
If the VM can determine the amount of pooled memory by malloc it would help with both determining if a trim_native_memory is needed, or there are some allocations happening outside of NMT.

It would be good if the VM can summarize the malloc pooled memory by using e.g. malloc_info(3).

We can thus more precise account for RSS value.
Comments
Changeset: b5a74269 Author: Johan Sjölen <jsjolen@openjdk.org> Date: 2023-02-20 14:23:54 +0000 URL: https://git.openjdk.org/jdk/commit/b5a7426996bb0e36319186756c46cfa7d0ab6e64
20-02-2023

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/12455 Date: 2023-02-07 15:00:14 +0000
07-02-2023