I just found Jitsi frozen after I opened my laptop. The UI is unresponsive, and the AWT EventQueue thread appears to be in a deadlock (full stack trace attached). That's running version 5350 on macos 10.9, with the bundled jre 1.8.
I saw the same thing yesterday, but I have never seen it before, which makes me thing that it is a relatively new feature. Has anyone seen something like this? Unless there is for some weird reason limited to my machine, I think we should fix it before pushing the new stable.
I don't see anything related in the commits after 5350, but let me know if there's a fix and I missed it.
Otherwise...any idea of what's the cause and how to fix it?
jitsi-deadlock (63.4 KB)