On Wed, 11 Mar 2026 15:05:15 GMT, Patricio Chilano Mateo <[email protected]> wrote:
> Please review the following small test fix. Test `SuspendResume3.java` can > deadlock due to `worker2` being suspended at the wrong place. This can happen > because `arriveAndAwaitAdvance()` may trigger additional class > loading/initialization, during which the thread can also appear as `BLOCKED` > and thus be suspended later on. If the main thread tries to access those same > classes before resuming `worker2` then the test will deadlock. I added the > specific scenario involving class `ForkJoinPool` to JBS including the > relevant stack traces. > > The fix is to use the management API to check `worker2` is blocked on the > specific monitor. > > The issue was observed by running local tests. I was able to reproduce it > locally and verified the issue is now fixed. > > Thanks, > Patricio This pull request has now been integrated. Changeset: 618a3fee Author: Patricio Chilano Mateo <[email protected]> URL: https://git.openjdk.org/jdk/commit/618a3feea9d46b38822a1d52b93ba2d12b34e000 Stats: 26 lines in 1 file changed: 25 ins; 0 del; 1 mod 8379795: Test SuspendResume3.java can timeout due to deadlock Reviewed-by: dholmes, sspitsyn ------------- PR: https://git.openjdk.org/jdk/pull/30199
