Gili Tzabari

Testcase: https://gist.github.com/cowwoc/743d2839bc7297a47516

@cloudhan Can you please clarify? Do you mean you don't plan to add this functionality?

Other UX suggestions: Provide options for the following functionality: 1. Groups all threads with similar stack-traces (as IntelliJ does). 2. Sort threads by their runtime duration, to identify potentially stuck/deadlocked...

You can get a list of all virtual threads with a mix of `jdk.internal.vm.ThreadContainers` and `jdk.internal.vm.ThreadContainer.threads()` using reflection. I know that invoking private APIs is not ideal, but I don't...

Hi again. Are you planning to work on Virtual Threads now that they are targeted as non-preview for JDK 21, and you just cut a new release of VisualVM?

Please see https://youtrack.jetbrains.com/issue/IDEA-305072. Maybe this is one and the same (JDK) bug? This is the application I am attaching VisualVM to.

@thurka I've posted an updated heap dump for your review at `[removed]`. Please let me know when you are done downloading it so I can remove the file. Thank you.

@thurka I again think that this issue is related to the JDK hang bug I referenced earlier. If you take a look at https://bugs.openjdk.org/browse/JDK-8296463 Fairoz Matte is only able to...

@thurka Okay, this is beginning to make more sense. Does VisualVM retain memory for dead threads? If so, increasing the maximum amount of memory won't help because ultimately it'll still...

> Yes, you can display data for dead threads, so the info for already dead threads are preserved. This will have to change. It doesn't matter how much memory we...