Webstorm freezing.

Scott Wells repo owner

Justin, the next time it happens can you attach/email the thread dumps? That will help me see what's going on in the JVM so I can see what I can do to resolve it. Thanks!

2019-10-16T00:44:13+00:00

Justin Julicher reporter

attached threadDumps-freeze-20191016-100728-WS-192.6817.13-IlluminatedCloudConnectionConfig.getSfdxConnectionConfigs-7sec.7z

How's this?

2019-10-16T00:46:01+00:00

Justin Julicher reporter

attached threadDumps-freeze-20191016-085834-WS-192.6817.13.7z

2019-10-16T00:47:06+00:00

Scott Wells repo owner

Hopefully so. Let me take a look and hopefully I'll see something useful. Thanks!

2019-10-16T00:50:23+00:00

Scott Wells repo owner

Okay, so the issue seems to be that the Salesforce CLI is taking a long time to return. There are numerous threads all trying to get a list of connections. One of those threads is executing the CLI and waiting for it to complete, and the other threads are waiting for that overall operation to complete so that they all have the connection list.

How long does sfdx force:org:list --json take to run for you? If it takes a while, here are some things to try to speed it up:

Run sfdx force:org:list --clean to remove any expired scratch orgs.
Look for any entries in the output of sfdx force:org:list that don't show as Connected and use sfdx force:auth:logout to remove them.

When I've seen this issue for other users in the past, SFDX had numerous stale entries that it was checking for validity, each in serial fashion, and it made force:org:list run quite long (in terms of minutes instead of seconds). Once users cleaned things up, it would run again in seconds. Because that's how IC gets its list of CLI-based orgs, a long runtime can make things seem like they're deadlocked when in fact they're just waiting for CLI completion.

I've spoken with folks on the SFDX team about this and they're planning(/hoping) to add a flag to force:org:list to have it enumerate the configured orgs without actually validating them. That would run almost instantaneously, and then when you actually use force:org:display to get details on a single given org, it would validate that one. Unfortunately that's not there yet...

Oh, and if force:org:list runs very quickly from the command-line for you, please enable debug logging for Salesforce DX, reproduce the issue, and provide your idea.log again so I can see why this critical thread from the thread dump is taking so long:

"ApplicationImpl pooled thread 3" prio=0 tid=0x0 nid=0x0 waiting on condition
     java.lang.Thread.State: TIMED_WAITING
    at java.base@11.0.3/java.lang.Thread.sleep(Native Method)
    at com.illuminatedcloud.util.CommandLineUtil.runCommandLine(SourceFile:130)
    at com.illuminatedcloud.intellij.sfdx.SfdxUtil.runSfdx(SourceFile:200)
    at com.illuminatedcloud.intellij.sfdx.SfdxUtil.runSfdx(SourceFile:285)
    at com.illuminatedcloud.intellij.sfdx.SfdxUtil.runSfdx(SourceFile:262)
    at com.illuminatedcloud.intellij.sfdx.SfdxUtil.runSfdx(SourceFile:226)
    at com.illuminatedcloud.intellij.sfdx.SfdxUtil.runSfdxForceOrgList(SourceFile:483)
    at com.illuminatedcloud.intellij.settings.application.IlluminatedCloudConnectionConfig.doGetSfdxConnectionConfigs(SourceFile:627)
    at com.illuminatedcloud.intellij.settings.application.IlluminatedCloudConnectionConfig.getSfdxConnectionConfigs(SourceFile:562)
    at com.illuminatedcloud.intellij.settings.application.IlluminatedCloudConnectionConfig.getConnectionConfigs(SourceFile:506)
    at com.illuminatedcloud.intellij.settings.application.IlluminatedCloudConnectionConfig.getConnection(SourceFile:681)

2019-10-16T01:04:23+00:00

Justin Julicher reporter

It was only taking about 5 seconds to run….. definitely not minutes. I wonder if it could be because I’m based in Australia and our org is in Frankfurt/Paris…. those long round trips do make a difference I think.

‌

2019-10-16T01:41:25+00:00

Scott Wells repo owner

Sorry, I crashed pretty early last night. If you're seeing a 5 second runtime force:org:list from the CLI, let's get a debug log to see what IC is doing when it hangs. My guess is that it'll just be polling for the CLI to complete, but let's verify that.

2019-10-16T14:12:47+00:00

Randy Lutcavich

Retrieving metadata in Webstorm often freezes up my computer as well. Especially if I’m running multiple instances of Webstorm. But only seems to happen when I send it to the background (using the Background button on the modal).