-
Enhancement
-
Resolution: Fixed
-
P4
-
17
-
b10
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8274049 | 11.0.14 | Thomas Stuefe | P4 | Resolved | Fixed | b01 |
However, the report uses the standard "K" scale, which is shouldn't, since this omits small leaks < 1K. Hence it should use scale=1. This would provide us with a precise exit report. Note that for this to work
- backported by
-
JDK-8274049 NMT: Final report should use scale 1
-
- Resolved
-
- relates to
-
JDK-8261334 NMT: tuning statistic shows incorrect hash distribution
-
- Resolved
-
-
JDK-8227031 Print NMT statistics on fatal errors
-
- Resolved
-
-
JDK-8261238 NMT should not limit baselining by size threshold
-
- Resolved
-
-
JDK-8261644 NMT: Simplifications and cleanups
-
- Resolved
-
-
JDK-8261661 gc/stress/TestReclaimStringsLeaksMemory.java fails because Reserved memory size is too big
-
- Resolved
-
- links to
-
Commit openjdk/jdk11u-dev/62207ef2
-
Commit openjdk/jdk/1740de2a
-
Review openjdk/jdk11u-dev/80
-
Review openjdk/jdk11u-dev/348
-
Review openjdk/jdk11u-dev/357
-
Review openjdk/jdk/2450