When I use jfr print to view events, the VirtualPinnedThreadEvent has the basic support for a stack trace, but the stack trace doesn't show why the thread was pinned -- e.g., which frame has the synchronized lock. That information is available from -Djdk.tracePinnedThreads, but I shouldn't need to run both diagnostics and then attempt to correlate the long-running JFR events with the stack trace output.