IntelliJ deadlocks multiple times per day - JetBrains claim it's IC2
Issue #1313
resolved
Initially reported here https://youtrack.jetbrains.com/issue/IDEA-216198
Thread dumps attached.
Essentially I'm getting multiple crashes per day forcing me to restart intelliJ. I've actually lost work over it before which is something completely new to me for IntelliJ - it's normally excellent at saving as I go.
Let me know if I can provide any more useful information.
Comments (7)
-
reporter
-
repo owner
Thanks for providing the context, Jonny. I'll take a look and see if I can figure out what's going on. Can you verify that you're on the latest builds of both IntelliJ IDEA and Illuminated Cloud 2 just to rule that out? My guess is that you are, but it's always worth starting there. Also, what OS is this?
-
reporter
Sorry Scott, I know you are still on vacation.
After updating my credentials I no longer crash in that project when opening an apex class. I'm still getting lots of crashes but I'm not convinced they are all IC2, I think jetbrains just looked at the most recent thread dump rather than the collection, where the most recent thread dump was the connection crash described in my earlier comment.
I think we could downgrade this to major, unless you think it's IC2 from the thread dumps as well?
I believe the native IntelliJ Jira integration just crashed my IntelliJ as I was typing this comment too :)
IntelliJ version info:
IntelliJ IDEA 2019.1 (Ultimate Edition) Build #IU-191.6183.87, built on March 26, 2019 Licensed to Traction on Demand Inc. / Jonny Power Subscription is active until November 16, 2019 JRE: 1.8.0_202-release-1483-b39 amd64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Windows 10 10.0
Illuminated Cloud 2 version info:
v2.0.6.3
-
repo owner
Okay. It might be helpful to get debug logs from when these are happening in addition to thread dumps. That way I can see the stack traces. Feel free to email them to support@illuminatedcloud.com, and include as many as makes sense to ensure I get the full context. It'll likely be later this weekend before I get a chance to look at them as I'm about to start the long flight home overnight...
-
repo owner
FYI, I was just able to reproduce something very much like this (hopefully the same thing) via
#1315. I'm trying to understand it now so that I can provide a good fix. -
repo owner
Okay, I have a prospective fix for this deadlock that will be in the next build (shooting for tomorrow morning).
-
repo owner
- changed status to resolved
I'm hoping that the changes made in 1.8.5.1/2.0.6.5 will resolve this. Please let me know if you see it occur again after updating.
- Log in to comment
Very reproducible when opening a project that is configured to an expired scratch org connection (metadata connection to scratch org) and quick navigating to an apex class. I'm seeing crashes in other scenarios too though, with less predictable causes.