JDK-6718125 : SA: jmap prints negative value for MaxNewSize
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 6u10,7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-06-23
  • Updated: 2023-08-18
  • Resolved: 2011-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 Other
6u14Fixed 7Fixed hs14Fixed
Related Reports
Duplicate :  
JDK-6788173 - jmap prints negative value of MaxNewSize for 64-bit VM
Relates :  
JDK-8237542 - JMapHeapConfigTest.java doesn't work with negative jlong values
Relates :  
JDK-6792386 - SA: jmap wrong output for MaxNewSize
Description
jmap <pid> prints negative number for MaxNewSize for 64bit vm. 

snip of jmap heap summary output:

Heap Configuration:
MinHeapFreeRatio = 40
MaxHeapFreeRatio = 70
...
MaxNewSize = -65536(-0.0625MB)
...
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/a2de7dfbfcf0
18-08-2008
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-svc/hotspot/rev/a2de7dfbfcf0
16-08-2008