JDK-8211756 : Release Note: G1 May Uncommit Memory During Marking Cycle
- Type: Sub-task
- Component: hotspot
- Sub-Component: gc
- Affected Version: 12
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2018-10-05
- Updated: 2019-04-09
- Resolved: 2018-11-14
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 12 |
|---|
12Resolved  |
Description
By default, G1 may now give back Java heap memory to the operating system during any concurrent mark cycle. G1 will respect default Java heap sizing policies at that time. This change improves memory usage of the Java process if the application does not need all memory. This behavior may be disabled in accordance with default heap sizing policies by setting minimum Java heap size to maximum Java heap size via the `-Xms` option.