| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8028665 | 8 | Jesper Wilhelmsson | P3 | Resolved | Fixed | b117 |
| JDK-8028974 | port-stage-ppc-aix | Jesper Wilhelmsson | P3 | Resolved | Fixed | master |
MaxNewSize parameter does not get set when uses parallel collector. 4GB reflects default value of (xuint)-1.
To reproduce the problem:
1. Run server VM on Solaris
2. Run jmap -heap <pid> to print out heap info
3. Check MaxNewSize value.
To reproduce the problem:
1. Run server VM on Solaris
2. Run jmap -heap <pid> to print out heap info
3. Check MaxNewSize value.
- backported by
-
JDK-8028665 jmap shows MaxNewSize=4GB when Java is using parallel collector
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
JDK-8005989 The default value for MaxNewSize should be less than or equal to MaxHeapSize
-
- Closed
-
- relates to
-
JDK-8012591 Flags shown by jmap are not updated after argument processing and ergonomics handling
-
- Closed
-
-
-
- Closed
-