JDK-8357650 : ThreadSnapshot to take snapshot of thread for thread dumps
  • Type: Sub-task
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 25
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-05-23
  • Updated: 2025-07-10
  • Resolved: 2025-06-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25 b26Fixed
Related Reports
Causes :  
JDK-8358588 - ThreadSnapshot.ThreadLock should be static nested class
Relates :  
JDK-8361913 - Thread.dump_to_file is not protected from mount/unmount
Description
jdk.internal.vm.ThreadSnapshot takes a snapshot of a thread (name, stack trace, state, locks) for use HotSpotDiagnosticMXBean.dumpThreads and jcmd Thread.dump_to_file. The class/implementation is currently in the loom repo, need to bring it to main line to allow the thread dump be updated to include lock information.
Comments
Changeset: 406f1bc5 Branch: master Author: Alex Menkov <amenkov@openjdk.org> Date: 2025-06-03 18:46:55 +0000 URL: https://git.openjdk.org/jdk/commit/406f1bc5b94408778063b885cdac807fd1501e44
03-06-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/25425 Date: 2025-05-24 00:17:26 +0000
24-05-2025