See attached stack dump, just locked up w/o warning, had to kill process to get dump.
Created attachment 44697 [details]
Sorry, I do not see any obvious (Java-level) deadlock in the thread dump. Some threads are waiting to lock object
0xd1c24ef0, which is not locked by any thread. AWT (also listed as waiting on 0xd1c24ef0) is even shown as RUNNABLE. If
it happens again, please try to get the thread dump using jstack with the "-m" parameter. Thanks.
Note that it can be a livelock and the thread dump was caught just after another cycle of unlocking 0xd1c24ef0, ot there
might be a heap space shortage which would slow down everything a lot.
*** This issue has been marked as a duplicate of 110074 ***