JDK-8204552 : NMT: Separate thread stack tracking from virtual memory tracking
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-06-07
  • Updated: 2019-08-15
  • Resolved: 2019-03-26
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 13
13 b14Fixed
Related Reports
Relates :  
JDK-8202772 - NMT thread stack tracking causes crashes on AIX
Description
From the very beginning, NMT treats thread stack as virtual memory allocation and tracks them in the same way as virtual memory.

However, it is not the case, pthread library does not dictate how stack is allocated (see the discussion [1] for details)

It should not be hard to pull thread stacks into another tracking list. Matter of fact, it might simplify a few things, as we started doing something special the thread stacks, e.g. figuring out actual stack range in used and where are guard pages. 

[1] http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2018-June/028407.html
Comments
Latest Webrev: http://cr.openjdk.java.net/~zgu/JDK-8204552/webrev.03/index.html Review thread: https://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2019-February/032663.html
14-03-2019
I re-open this bug, because current stack tracking breaks AIX.
12-02-2019
Sorry, this is definitely on the bottom of my list for a while. I intent to get back to some NMT related works in 13 timeframe, will reopen it then.
30-01-2019
In the past the number of open bugs/enhancements just kept growing, so we (runtime team) adopted a general approach to close things when it was clear they were not on anyone's radar for actually fixing. They would still be available to search and could be re-opened if someone wanted to take them up.
30-01-2019
I don't get it. Can't JBS be used as a backlog? It's fair game to leave enhancements open for some time is it not?
30-01-2019
The bug is assigned but 7 months old with no sign it is being worked on. If the assignee intends to actually work on this they can reopen.
30-01-2019
I agree with Severin. I would have thought that Bugs which have an Assignee already (a non-dead one) do not get closed, just moved to another release?
30-01-2019
I'm not sure this is the right move to close as "Won't fix". Why can't this enhancement tracking be kept open? It would be a community member providing the implementation after all.
30-01-2019
I understand you, but that is unfortunate. Maybe a pragmatic way would be to leave it open but set priority to low (which it obviously is since noone works on it) and set fix versions as tbd.
30-01-2019
Runtime Triage: This is not on our current list of priorities. We will consider this feature if we receive additional customer requirements.
29-01-2019