-
Bug
-
Resolution: Not an Issue
-
P4
-
None
-
7
-
generic
-
generic
After fix to 6788173, jmap still does not print value of MaxNewSize correctly.
Heap Configuration:
MinHeapFreeRatio = 40
MaxHeapFreeRatio = 70
MaxHeapSize = 1029701632 (982.0MB)
NewSize = 2686976 (2.5625MB)
MaxNewSize = 17592186044415 MB
OldSize = 5439488 (5.1875MB)
...
There are two problems now:
1. Format is wrong. Before the fix (and all other memory parameters, previously and now) are shown as
"bytes (mbytes MB)"
or "bytes (gbytes GB)"
2. The value is unreasonably big. It's bigger than MaxHeapSize.
Heap Configuration:
MinHeapFreeRatio = 40
MaxHeapFreeRatio = 70
MaxHeapSize = 1029701632 (982.0MB)
NewSize = 2686976 (2.5625MB)
MaxNewSize = 17592186044415 MB
OldSize = 5439488 (5.1875MB)
...
There are two problems now:
1. Format is wrong. Before the fix (and all other memory parameters, previously and now) are shown as
"bytes (mbytes MB)"
or "bytes (gbytes GB)"
2. The value is unreasonably big. It's bigger than MaxHeapSize.
- relates to
-
JDK-6788173 jmap prints negative value of MaxNewSize for 64-bit VM
- Closed
-
JDK-6718125 SA: jmap prints negative value for MaxNewSize
- Closed