RFR(XS) 8224247: AllocateOldGenAt fires assertion failure

Kharbas, Kishor kishor.kharbas at intel.com
Tue May 28 15:40:28 UTC 2019


Hi,

Requesting review for,
CR : https://bugs.openjdk.java.net/browse/JDK-8224247
Webrev : http://cr.openjdk.java.net/~kkharbas/8224247/webrev.00

Changeset 54678 for https://bugs.openjdk.java.net/browse/JDK-8198505 replaced the two methods in CollectorPolicy - max_heap_byte_size() and heap_reserved_size_bytes(), with a single method heap_reserved_size_bytes() in [g1/parallel]Arguments.

The second method was introduced in https://bugs.openjdk.java.net/browse/JDK-8202286 to differentiate between the size of reserved memory (heap_reserved_size_bytes(), which might be 2x of MaxHeapSize) and the max size heap can grow (heap_reserved_size_bytes(), which is always MaxHeapSize). When 'AllocateOldGenAt' flag is used, during heap initialization we need the first size and later on the second size. Adding the second method back fixes the issue.

The fix is just adding a new method and using it during initialization of G1 and PS heap, but the existing method's name is more appropriate for the new method. So I renamed existing method. This would also avoid confusion about these methods down the line.

Please suggest alternated approach if you see one.

Thanks,
Kishor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20190528/518a33f1/attachment.htm>


More information about the hotspot-gc-dev mailing list