[jdk8u-dev] RFR: 8358568: C2 compilation hits "must have a monitor" assert with -XX:-GenerateSynchronizationCode
Severin Gehwolf
sgehwolf at openjdk.org
Wed Jul 2 16:10:47 UTC 2025
On Wed, 2 Jul 2025 04:30:56 GMT, hanguanqiang <duke at openjdk.org> wrote:
> This PR fixes JDK-8358568, a JVM crash triggered when running with -XX:-GenerateSynchronizationCode
>
> Problem:
> When synchronization code generation is disabled by -XX:-GenerateSynchronizationCode, the compiler’s do_monitor_exit() method still tries to access monitor objects without checking if any monitors exist.This causes an assertion failure and JVM crash.
>
> Root Cause:
> Parse::do_monitor_exit() calls shared_unlock() using monitor info unconditionally,but with GenerateSynchronizationCode disabled, no monitor info is available, leading to invalid access.
>
> Fix
> Add a check in do_monitor_exit() to skip monitor unlocking if GenerateSynchronizationCode is false, avoiding invalid monitor access and preventing the crash.
Please fix this issue in jdk head. Repo is:
https://github.com/openjdk/jdk
Once a fix is in the latest JDK a backport can be proposed.
-------------
PR Comment: https://git.openjdk.org/jdk8u-dev/pull/664#issuecomment-3028437671
More information about the jdk8u-dev
mailing list