RFR: 8366659: ObjectMonitor::wait() can deadlock with a suspension request [v4]
Anton Artemov
duke at openjdk.org
Tue Nov 11 13:13:34 UTC 2025
On Tue, 11 Nov 2025 02:33:25 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:
>> Anton Artemov has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 18 commits:
>>
>> - Merge remote-tracking branch 'origin/master' into JDK-8366659-OM-wait-suspend-deadlock
>> - 8366659: Added a comment to a boolean arg for enter()
>> - Merge remote-tracking branch 'origin/master' into JDK-8366659-OM-wait-suspend-deadlock
>> - Merge remote-tracking branch 'origin/master' into JDK-8366659-OM-wait-suspend-deadlock
>> - 8366659: Fixed new lines.
>> - Merge remote-tracking branch 'origin/master' into JDK-8366659-OM-wait-suspend-deadlock
>> - 8366659: Removed incorrect assert,
>> - 8366659: Fixed merge conflict
>> - 8366659: Fixed whitespace.
>> - 8366659: Disabled posting JVMTI events in reenter-etner path of wait. Postponed waited event.
>> - ... and 8 more: https://git.openjdk.org/jdk/compare/79fee607...31482ba4
>
> test/hotspot/jtreg/serviceability/jvmti/SuspendWithObjectMonitorWait/SuspendWithObjectMonitorWait.java line 452:
>
>> 450:
>> 451: try { Thread.sleep(1000);
>> 452: } catch(Exception e) {}
>
> Nit: The Thread.sleep call should be on its own line after L451.
Addressed in the latest commit.
> test/hotspot/jtreg/serviceability/jvmti/SuspendWithObjectMonitorWait/SuspendWithObjectMonitorWait.java line 506:
>
>> 504: }
>> 505: try { Thread.sleep(1000);
>> 506: } catch(Exception e) {}
>
> Nit: The Thread.sleep call should be on its own line after L505.
Addressed in the latest commit.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/27040#discussion_r2514175972
PR Review Comment: https://git.openjdk.org/jdk/pull/27040#discussion_r2514176496
More information about the serviceability-dev
mailing list