-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VisualVM freezes if JVM stops while connecting #616
Comments
Do you have steps to reproduce it? According to thread dump, it is blocked in native code deep in JDK. It is not immediatelly clear to me, how to prevent it. |
Well its reproducable with the shown VerifyTests of JDT, which spawn new JDK like every second. But i have not minimal reproducer yet. A "solution"/workaround would be to have the connect in a different thread that does not block the ui. At worst such thread would just not die. |
Hmm, "DataSourceWindowManager Processor" is not AWT thread. |
Hmm, i tried to create a reproducer by just restarting shortliving JVMs, but i can NOT reproduce with such simple program :-( :
|
The AWT thread is waiting for a lock hold by the starting thread:
|
This shows how important is to post whole thread dump, not just the part you think is important. So, please post the whole thread dump. Thanks. |
i did that, see "visualVMFreeze.log" in the issue |
OK, this link without description is almost invisble. :-) |
Any update on the steps how to reproduce it? |
I clicked on a local JVM. Typically it takes some seconds to connect, which is fine. But when the target JVM terminates during that time VisualVm freezes and all previous recorded measurements are lost :-(
I took a jstack from VisualVM while it is frozen:
visualVMFreeze.log
The text was updated successfully, but these errors were encountered: