WEBSTORM Java Exception on clicking retrieve metadata button

[Chris Tufts]

I am seeing an inconsistent error that webstorm crashes when I attempt to retrieve metadata, unsure what the culprit is as it seems fairly random, and has occurred on two windows computers now. (just happened to upgrade since I noticed it)

I don’t do anything in consistent pattern save potentially flipping to webstorm from salesforce and clicking the button right away.

I have attached both crash logs.

let me know if you need help trying to narrow anything down. seems to only occur on retrieve and I am using an sfdx project with an org that I attached via a web auth login.

[Scott Wells]

I've heard about similar from one or two other users. It appears that there may be an issue with the JetBrains OpenJDK on certain Intel hardware. You can find out more here:

https://youtrack.jetbrains.com/issue/JBR-2310

I have a Surface Laptop 3 and had also been experiencing numerous crashes of both the IDE and even the entire OS.

The solution is to get an OS update that includes Intel microcode 50, but that's not available for all OSes. It's out for Mac and some Linux distributions, but I don't think any Windows machines have it yet (including my Surface Laptop 3).

The workaround is to add these JVM arguments for the IDE:

-XX:-TieredCompilation, -XX:TieredStopAtLevel=1 and -XX:UseAVX=2

using Help>Edit Custom VM Options. Please try that and let me know if it doesn't resolve the issue for you. I've also followed up with JetBrains to let them know that more users are experiencing this hard JVM crash.

[Chris Tufts]

upgraded this to critical as it now seems that I cannot retrieve metadata without this crash occurring, its not blocking as I can obviously retrieve the metadata in other ways.

[Scott Wells]

Looks like we just crossed messages. Unfortunately this is a hard JVM crash that seems to have started with the 2020.2 JetBrains IDEs for a small number of people, specifically Windows users. I'm aware of three things that might help:

1. Adding the JVM args in my previous comment to 2020.2.
2. Changing to an Oracle host JVM vs. the bundled JetBrains OpenJDK JVM.
3. Downgrading to 2019.3.5 for sure and perhaps just down to 2020.1.

I personally have done the first and haven't seen the issue any longer. I've heard from two other users that it has resolved the issue for them as well.

[Chris Tufts]

Johnny on the spot as usual Scott! (after I of course corrupted my config file and took 10 minutes to figure out where the heck windows saves it ./facepalm…)

And yes I came back to the browser and commented before seeing your prior comment. Resolving for now, hopefully intel/windows/java resolve their issue soon.

[Chris Tufts]

per Scott's workaround, this resolved the issue

[Scott Wells]

Good to know, and actually good to know that this crash happens consistently for you. I'll see if I can reproduce it by removing those JVM args temporarily and, if so, hopefully I can give JetBrains a reproducible test case so they can fix this for good.

[Scott Wells]

Unfortunately I wasn't able to reproduce the issue even after removing those JVM args. I'm chatting with JetBrains support now about the underlying issue.