JDK24 thrstatetest_0_FAILED Failed to destroy JVM

[JasonFengJ9]

Failure link

From an internal build(ubu22-aarch64-5):

20:25:36  openjdk version "24-internal" 2025-03-18
20:25:36  OpenJDK Runtime Environment (build 24-internal-adhoc.jenkins.BuildJDK24aarch64linuxPersonal)
20:25:36  Eclipse OpenJ9 VM (build master-6d451b1c077, JRE 24 Linux aarch64-64-Bit Compressed References 20241212_4 (JIT enabled, AOT enabled)
20:25:36  OpenJ9   - 6d451b1c077
20:25:36  OMR      - 7e3c8005277
20:25:36  JCL      - c504eab20b8 based on jdk-24+27)

Rerun in Grinder - Change TARGET to run only the failed test targets.

Optional info

Failure output (captured from console output)

23:29:44  ===============================================
23:29:44  Running test thrstatetest_0 ...
23:29:44  ===============================================
23:29:44  thrstatetest_0 Start Time: Fri Dec 13 04:29:44 2024 Epoch Time (ms): 1734064184136
23:29:44  variation: Mode110
23:29:44  JVM_OPTIONS:  -Xjit -Xgcpolicy:gencon -Xnocompressedrefs 

23:29:45  306/306 Tests passed. 0 Failures ignored. 123 Failures expected.
23:29:45  ALL TESTS COMPLETED AND PASSED
23:29:48  Failed to destroy JVM
23:29:48  -----------------------------------
23:29:48  thrstatetest_0_FAILED

50x internal grinder - not an intermittent problem, fails every time

[pshipton]

Assuming VM, at least we can start there.
@tajila

[gacholio]

If I had to guess, I would think this is caused by the test spawning threads and exitting without properly shutting them down. Sometimes the timing is lucky, sometimes not. Java threads should be joined, and native threads should synchronize the exit via a monitor and j9thread_exit.

[tajila]

@h3110n3rv3 Please take a look at this

[h3110n3rv3]

yes I can take a look

[babsingh]

This issue should be fixed by #21044.