JDK-8187685 : NMT: Tracking compiler memory usage of thread's resource area
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 10
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-09-19
  • Updated: 2019-11-18
  • Resolved: 2017-10-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.
JDK 10 JDK 8
10 b31Fixed 8u172Fixed
Related Reports
Relates :  
JDK-8204128 - NMT might report incorrect numbers for Compiler area
Description
Vladimir Kozlov wrote:
> Compilers also use a lot thread local ResourceArea -
> Thread::current()->resource_area() and NEW_RESOURCE_ARRAY() macro.
> But thread local area is defined as mtThread:

> Thread() is called from CompilerThread() and we can pass a parameter to 
> indicate user. Or add a virtual method to Thread class to check type of 
> thread.
> 
> In the past we had compiler local changes to get information how much 
> memory was used during compilation but it was never get pushed. We 
> accessed Arena::_bytes_allocated for that.


Following email thread for details:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2017-September/028360.html