-
Bug
-
Resolution: Fixed
-
P4
-
8
-
b03
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8000378 | 8 | Christian Tornqvist | P4 | Closed | Fixed | b59 |
JDK-8017843 | 7u45 | Nils Loodin | P4 | Closed | Fixed | b01 |
JDK-8004386 | 7u40 | Nils Loodin | P4 | Closed | Fixed | b04 |
JDK-8000200 | hs25 | Christian Tornqvist | P4 | Closed | Fixed | master |
JDK-8004112 | hs24 | Nils Loodin | P4 | Closed | Fixed | master |
I was trying out NMT a few days ago but couldn't get it to work until I realised I gave it the wrong option, and it swallowed it silently but didn't do anything.
I was trying to use -XX:NativeMemoryTracking=details instead of -XX:NativeMemoryTracking=detail because because of a typo in a pdf.
It would be much friendlier if we failed explicitly and printed out the offending option given.
I was trying to use -XX:NativeMemoryTracking=details instead of -XX:NativeMemoryTracking=detail because because of a typo in a pdf.
It would be much friendlier if we failed explicitly and printed out the offending option given.
- backported by
-
JDK-8000200 Make NMT a bit friendlier to work with
-
- Closed
-
-
JDK-8000378 Make NMT a bit friendlier to work with
-
- Closed
-
-
JDK-8004112 Make NMT a bit friendlier to work with
-
- Closed
-
-
JDK-8004386 Make NMT a bit friendlier to work with
-
- Closed
-
-
JDK-8017843 Make NMT a bit friendlier to work with
-
- Closed
-
- relates to
-
JDK-8004053 -XX:NativeMemoryTracking:off doesn't work after fix for 7200092
-
- Closed
-
(1 relates to)