In the GitHub actions job on several PRs against JDK mainline (26), the test/jdk/java/lang/Thread/virtual/stress/GetStackTraceALotWhenBlocking.java test has been timing out frequently.

From one such failed run, here's the snippet of the jtr file. The complete jtr file is attached to this issue.

#section:main
----------messages:(10/425)----------
command: main GetStackTraceALotWhenBlocking 100000
reason: User specified action: run main/othervm/timeout=300 GetStackTraceALotWhenBlocking 100000
started: Fri Aug 29 15:26:41 UTC 2025
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules jdk.management
Process id: 14646
Timeout information:
--- Timeout information end.
finished: Fri Aug 29 15:48:23 UTC 2025
elapsed time (seconds): 1302.403

...

----------System.out:(1247/58401)----------
2025-08-29T15:26:42.616378Z => 52 of 100000
2025-08-29T15:26:43.621979Z => 96 of 100000
2025-08-29T15:26:44.649696Z => 138 of 100000
2025-08-29T15:26:45.661083Z => 180 of 100000
...
2025-08-29T15:48:17.554792Z => 76751 of 100000
2025-08-29T15:48:20.750377Z => 82586 of 100000
2025-08-29T15:48:23.860463Z => 90625 of 100000
...
result: Error. Program `/Users/runner/work/jdk/jdk/bundles/jdk/jdk-26.jdk/Contents/Home/bin/java' timed out (timeout set to 1200000ms, elapsed time including timeout handling was 1302393ms).


test result: Error. Program `/Users/runner/work/jdk/jdk/bundles/jdk/jdk-26.jdk/Contents/Home/bin/java' timed out (timeout set to 1200000ms, elapsed time including timeout handling was 1302393ms).

The test doesn't complete even after running for more than 20 minutes.