From ahakimunlu at gmail.com  Fri Dec 27 21:02:03 2024
From: ahakimunlu at gmail.com (=?UTF-8?B?QWJkw7xsaGFraW0gw5xubMO8?=)
Date: Sat, 28 Dec 2024 00:02:03 +0300
Subject: JVM crash - fatal error: Mark stack space exhausted.
Message-ID: <CAKnsem5yXOM-nP9eHQgAm-UXQeL892R1-TgA9npBpi9fAEHY8g@mail.gmail.com>

Hi,
I am not sure if this is the right place to post this issue. We are testing
out ZGC in a Xmx975G JVM. It crashed with the attached hs_err file.

#  Internal Error (zMarkStackAllocator.cpp:81), pid=34334, tid=38183
> #  fatal error: Mark stack space exhausted. Use
> -XX:ZMarkStackSpaceLimit=<size> to increase the maximum number of bytes
> allocated for mark stacks. Current limit is 8192M.


How can I find the right size for ZMarkStackSpaceLimit, so that jvm does
not crash?

Can ZGC handle this case in a more graceful way ? Can ZGC
adjust ZMarkStackSpaceLimit dynamically ? I mean, in a production
environment, we cannot keep crashing JVM until we find the right
ZMarkStackSpaceLimit value.

thanks,
Abdulhakim Unlu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/zgc-dev/attachments/20241228/a379659c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hs_err_pid34334.log.tar.gz
Type: application/gzip
Size: 2873218 bytes
Desc: not available
URL: <https://mail.openjdk.org/pipermail/zgc-dev/attachments/20241228/a379659c/hs_err_pid34334.log.tar-0001.gz>