RFR: 8359870: JVM crashes in AccessInternal::PostRuntimeDispatch [v7]
Serguei Spitsyn
sspitsyn at openjdk.org
Tue Jul 1 09:33:31 UTC 2025
On Mon, 30 Jun 2025 11:24:28 GMT, Kevin Walls <kevinw at openjdk.org> wrote:
>> ThreadDumper/ThreadSnapshot need to handle a failure to resolve the native VM JavaThread from a java.lang.Thread. This is hard to reproduce but a thread that has since terminated can provoke a crash. Recognise this and return a null ThreadSnapshot.
>
> Kevin Walls has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains 13 additional commits since the last revision:
>
> - remove test definition changes
> - TLH: use cv_internal_thread_to_JavaThread()
> - Merge remote-tracking branch 'upstream/master' into 8359870_threadexited
> - Test requires: permit linux debug testing
> - comment update
> - comment update
> - newline
> - Test fails on minimal VM: require jvmti feature
> - Correct THROW macro
> - ThreadDumper thread count
> - ... and 3 more: https://git.openjdk.org/jdk/compare/88ec329a...e2043438
Looks good.
test/jdk/com/sun/management/HotSpotDiagnosticMXBean/DumpThreadsWithEliminatedLock.java line 172:
> 170: }
> 171: }
> 172:
Nit: It seems that an unneeded extra empty line was added at the end of file.
-------------
Marked as reviewed by sspitsyn (Reviewer).
PR Review: https://git.openjdk.org/jdk/pull/25958#pullrequestreview-2974497586
PR Review Comment: https://git.openjdk.org/jdk/pull/25958#discussion_r2176996670
More information about the serviceability-dev
mailing list