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: 2011-03-08
- 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.
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 :
|
|
|
Relates :
|
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
|