-
Enhancement
-
Resolution: Fixed
-
P4
-
21, 22
-
b24
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8351557 | 21.0.8 | Andreas Steiner | P4 | Resolved | Fixed | master |
Interpreting the memory map correctly can help when used as a complement to other tools (e.g. NMT). There even exist tools out there that attempt to annotate the process memory map with JVM information.
That, however, can be much more easily and accurately done within the JVM. At least for mappings originating from hotspots, we have the relevant information in NMT.
- backported by
-
JDK-8351557 Add jcmd to print annotated process memory map
-
- Resolved
-
- relates to
-
JDK-8319948 jcmd man page needs to be updated
-
- Resolved
-
-
JDK-8322811 jcmd System.dump_map help info has conflicting statements
-
- Resolved
-
-
JDK-8319873 Add windows implementation for jcmd System.map and System.dump_map
-
- Resolved
-
-
JDK-8319875 Add macOS implementation for jcmd System.map
-
- Resolved
-
-
JDK-8322475 Extend printing for System.map
-
- Resolved
-
-
JDK-8326586 Improve Speed of System.map
-
- Resolved
-
-
JDK-8334026 Provide a diagnostic PrintMemoryMapAtExit switch on Linux
-
- Resolved
-
- links to
-
Commit openjdk/jdk/6f863b2a
-
Commit(master) openjdk/jdk21u-dev/dee3212e
-
Review openjdk/jdk/16301
-
Review(master) openjdk/jdk21u-dev/1415