> Before posting the VM_DEATH event the JVMTI code spins for up to 60 seconds > to allow in-progress callbacks to complete. If one of those callbacks > requires a safepoint while executing, then it will not be able to attain it > until the 60s spin is over - thus causing an apparent "hang" at VM > termination. The simple fix is to insert a `ThreadBlockInVM` in the loop so > that safepoint requests are honored. > > Testing: > - tiers 1-5 > - new regression test > > Thanks. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai).
David Holmes has updated the pull request incrementally with one additional commit since the last revision: reword comment for clarity ------------- Changes: - all: https://git.openjdk.org/jdk/pull/31982/files - new: https://git.openjdk.org/jdk/pull/31982/files/cd0ceb0d..9f0458f0 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=31982&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=31982&range=00-01 Stats: 2 lines in 1 file changed: 1 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/31982.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/31982/head:pull/31982 PR: https://git.openjdk.org/jdk/pull/31982
