-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Java-level deadlock #680
Comments
👤 sebastian.thomschke 🕗 Feb 24, 2014 at 15:46 UTC 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:"Worker-65": Java stack information for the threads listed above:"Worker-65": Found 1 deadlock. |
👤 sebastian.thomschke 🕗 Feb 24, 2014 at 15:46 UTC |
👤 sebastian.thomschke 🕗 Feb 24, 2014 at 15:53 UTC Using Lombok 1.12.4 |
👤 r.spilker 🕗 Feb 24, 2014 at 22:17 UTC Issue #566 has been merged into this issue. |
👤 r.spilker 🕗 Feb 24, 2014 at 22:20 UTC 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! |
👤 r.spilker 🕗 Feb 25, 2014 at 20:32 UTC We've updated the code. Please download the latest edge: |
👤 sebastian.thomschke 🕗 Feb 25, 2014 at 20:33 UTC The bug is not reliable at all. It happens maybe two times a week. I now installed the edge version. If I don't experience the bug again within the next week I think your change fixed it. |
👤 r.spilker 🕗 Feb 27, 2014 at 20:42 UTC We think this is fixed. Awaiting more community feedback before closing the issue. |
👤 sebastian.thomschke 🕗 Feb 27, 2014 at 22:48 UTC I extensively used SVN updates on large projects in the last two days and did not encounter the problem anymore. I too think it is fixed. Good job and thanks for the prompt resolution!!! |
👤 r.spilker 🕗 Mar 10, 2014 at 10:17 UTC |
👤 redlabbe 🕗 Apr 01, 2014 at 09:18 UTC I also had a deadlock (same stacktrace, not using svn, I doubt it has something to do with that, I'm using git) |
👤 juraj.misur 🕗 May 07, 2014 at 11:05 UTC Had the same deadlock in STS 3.5.1. After upgrade to 1.12.6 it's ok. |
End of migration |
…ok#706) Fixes projectlombok#680 Add support for lombok.builder.className config property
Migrated from Google Code (issue 645)
The text was updated successfully, but these errors were encountered: