JDK-8211331 : Add JFR event to track Unsafe memory allocations
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: jfr
  • Affected Version: 12
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2018-10-01
  • Updated: 2021-01-07
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-8222736 - Need more granularity to know when to spend time on JFR computations needed by specific events
Description
Maybe this falls into a more general category, such as Native Memory / NMT integration. Request is to trace Unsafe memory allocations / deallocations, filing for tracking purposes.
Comments
Webrev: http://cr.openjdk.java.net/~gziemski/8211331_rev1
10-05-2019
I'd like a clarification here: is the idea here to track every single allocation, or how much memory was allocated within some period? I hope it's the former, or otherwise we might be generating tons of events.
10-04-2019
Right now, Unsafe_AllocateMemory/Unsafe_ReallocateMemory are sole allocation recorded under mtOther, should be enough from NMT point of view.
07-02-2019