RFR: 8369515: Deadlock between JVMTI and JNI ReleasePrimitiveArrayCritical
Richard Reingruber
rrich at openjdk.org
Thu Dec 18 00:14:21 UTC 2025
On Fri, 12 Dec 2025 04:20:11 GMT, David Holmes <dholmes at openjdk.org> wrote:
> As discussed in JBS the deadlock occurs when the call to `ReleasePrimitiveArrayCritical` performs the transition from native to VM, and in the process checks for special runtime exit conditions - which includes the `obj_deopt_suspend` request. The simple solution is to define a custom JNI ENTRY with custom `ThreadInVMfromNative` that elides the exit check.
>
> The change is limited to `ReleasePrimitiveArrayCritical` and `ReleaseStringCritical`.
>
> There is no regression test as this has only been seen in long running stress tests.
>
> Testing:
> -tiers 1-6
Thanks! Same with my testing.
I doubt that I'll find the time to write a reproducer though.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/28779#issuecomment-3667664024
More information about the serviceability-dev
mailing list