Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Java-level deadlock #680
What steps will reproduce the problem?
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
Creating a threaddump reveals the following deadlock:
Found one Java-level deadlock:
Java stack information for the threads listed above:
Found 1 deadlock.
We tried reproducing this and succeeded. (Actually a different issue with STS and the Gradle plugin. jstack did not report a deadlock, but eclipse is completely stuck with no CPU cycles same as a deadlock, so we're assuming it's related).
And then we failed. So, unfortunately, it looks like this will occur or not based on a race condition. We've eliminated the lock on the 'a Hashmap' in your deadlock report by using a j.u.concurrent alternative. Maybe this will fix things.
How reliably does this bug occur on your computer when you try and reproduce it? Can you tell us how reliable it is, and then give this edge release a shot to see if that fixes the problem? Thanks, owe you a beer!