JDK-8048088 : Conservative maximum heap alignment should take vm_allocation_granularity into account
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8u40,9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: windows
- Submitted: 2014-06-25
- Updated: 2015-01-21
- Resolved: 2014-07-21
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 8 | JDK 9 |
|---|---|
8u40Fixed  |
9 b26Fixed |
Description
The conservative max heap alignment does not take the alignment requirement imposed by the OS into account when calculating it. This may cause some assertions to fail. Note that actually no crash has been observed yet, as other alignment requirements are at this time larger than the maximum value of vm allocation granularity (64k vs. 2M).
Comments
|