On Wed, 13 May 2026 17:35:40 GMT, Chris Plummer <[email protected]> wrote:
> After receiving the expected 4 ThreadDeathEvents, the test disables the > ThreadDeathRequest and stops processing events. However, there is already > another ThreadDeathEvent in flight for the UsageTracker thread. That results > in suspending all debuggee threads, with the expectation that the debugger > will eventually process the event and do an eventSet.resume(). That never > happens, leaving the debuggee suspended while the debugger waits for the > debuggee to send a DONE command, which it can't because it is suspended. > > After disabling the ThreadDeathRequest, the debuggee needs to make sure all > pending events get processed. > > Tested by running thread001 about 600 times with JTREG_USAGE_TRACKER=true > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). This pull request has now been integrated. Changeset: 29a7130d Author: Chris Plummer <[email protected]> URL: https://git.openjdk.org/jdk/commit/29a7130d986ab8d1684498cdf9482c6baa121320 Stats: 13 lines in 1 file changed: 12 ins; 0 del; 1 mod 8330363: JDI ThreadDeathEvent/thread/thread001 timed out with UT enabled Reviewed-by: sspitsyn, lmesnik ------------- PR: https://git.openjdk.org/jdk/pull/31156
