-
Bug
-
Resolution: Fixed
-
P4
-
8u40, 9
-
b26
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8056662 | emb-9 | Unassigned | P4 | Resolved | Fixed | b26 |
JDK-8063378 | 8u45 | Thomas Schatzl | P4 | Resolved | Fixed | b01 |
JDK-8051706 | 8u40 | Thomas Schatzl | P4 | Resolved | Fixed | b02 |
JDK-8070937 | emb-8u47 | Thomas Schatzl | P4 | Resolved | Fixed | team |
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).
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).
- backported by
-
JDK-8051706 Conservative maximum heap alignment should take vm_allocation_granularity into account
-
- Resolved
-
-
JDK-8056662 Conservative maximum heap alignment should take vm_allocation_granularity into account
-
- Resolved
-
-
JDK-8063378 Conservative maximum heap alignment should take vm_allocation_granularity into account
-
- Resolved
-
-
JDK-8070937 Conservative maximum heap alignment should take vm_allocation_granularity into account
-
- Resolved
-