Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P4
Fix Version/s: 9
Affects Version/s: 8u40, 9
Component/s: hotspot
Labels:
- gc-g1
- noreg-other

Subcomponent:
gc
Resolved In Build:
b26
OS:

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).

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

Assignee:: Thomas Schatzl

Reporter:: Thomas Schatzl

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2014-06-25 03:52

Updated:: 2015-01-21 09:53

Resolved:: 2014-07-21 03:11

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates