-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
6u10
-
generic
-
generic
jmap prints negative value for MaxNewSize for 64-bit VM (all collectors) (here, VM is started without -XX:MaxNewSize=)
using thread-local object allocation.
Parallel GC with 2 thread(s)
Heap Configuration:
MinHeapFreeRatio = 40
MaxHeapFreeRatio = 70
MaxHeapSize = 536870912 (512.0MB)
NewSize = 2686976 (2.5625MB)
MaxNewSize = -65536 (-0.0625MB)
...
using thread-local object allocation.
Parallel GC with 2 thread(s)
Heap Configuration:
MinHeapFreeRatio = 40
MaxHeapFreeRatio = 70
MaxHeapSize = 536870912 (512.0MB)
NewSize = 2686976 (2.5625MB)
MaxNewSize = -65536 (-0.0625MB)
...
- duplicates
-
JDK-6718125 SA: jmap prints negative value for MaxNewSize
-
- Closed
-
- relates to
-
JDK-6792386 SA: jmap wrong output for MaxNewSize
-
- Closed
-