Webstorm so slow I can't use it.

Hi, Webstorm is killing my CPU since my last update . It's basically unusable. Even if I open 1 file in editor,  my CPU starts running out of control.

I am on Mac OSX Sierra 10.12.  Please help 

23 comments
Comment actions Permalink

Thanks! can i upload the zip to this thread ?

0
Comment actions Permalink

I uploaded via your webform. it is called latest.zip. Thanks

0
Comment actions Permalink

Extremely Slow. Complete Can't Work With It Anymore !!!  After upgraded to 2016.3.3, it became slower and slower and the whole app just froze at a high frequent. 

My system is the same as Doug's. 

 

 

0
Comment actions Permalink

@Woohling please provide CPU snapshots (see above)

0
Comment actions Permalink

Too Complicated to follow your instructions ..... May I just posted some screenshot I took ? when the app is dead, the CPU percentage is extremely high. And when the app is currently active, the CPU percentage is not low either.

 





0
Comment actions Permalink

Screenshots won't help here. Sorry, but they are as useful as a photo of your pet. CPU 30.83% - so what?

-9
Comment actions Permalink

Maybe as a professional in JB, you clearly know it won't help. But I thought it might help so I posted in my convenient.  But as a customer, and a firm supporter for webstorm, I always like your app, and your CPU screenshot solution is way too completed, not every one is a rocket scientist in your area. Maybe your could kindly point out that it won't work, but your sarcastic answer is really making me feels quite uncomfortable and unpolite. And quite lower my affection for webstorm. 

 

 

12
Comment actions Permalink

DId you look at my uploaded zip file yet ????

0
Comment actions Permalink

Missed your post, sorry!

The problem looks similar to https://youtrack.jetbrains.com/issue/WEB-24880 that is fixed in 2017.1. Please can you check if the problem persist when using EAP?

If upgrading doesn't help, please try disabling 'Unused JavaScript/ActionScript global symbol' inspection (Preferences | Editor | Inspections, JavaScript/General) - does it make things any better?

0
Comment actions Permalink

so far so good. thanks!

0
Comment actions Permalink

Any updates to making WebStorm usable? It's unbearably slow on i7 with 16GB RAM and every version release is worse. I followed the instructions and I can only see Memory Shanpshot option in the Tools menu and can't do CPU Snapshot to upload.

0
Comment actions Permalink

Seems you didn't enable the Profiler Agent in .vmoptions per instructions. Please open Help | Edit custom VM options and see if the -agentlib:yjpagent64 (or whatever option is suitable for your OS/JDK version) is there

0
Comment actions Permalink

Wanted to add to this... I noticed that WebStorm had been very slow recently and came across this thread. I saw that there was and upgrade available, so I upgraded and the problem noticeably persisted.

 

Disabling 'Unused JavaScript/ActionScript global symbol' as suggested *immediately* resolved the slowness, and my CPU immediately stopped spinning.

 

Looking forward to a patch to resolve it with that option enabled, but thank you for the work around!

0
Comment actions Permalink

Same problem here, I´ve been using both WebStorm and PhpStorm for a while since the intellisense was way better than many others but it has come to a point where these tools actually slows down my overall progress at work, for quite some time I accepted that it took a sec just to move the I-beam, having to click several times on popup menu items the constant hogging of CPU but this doesn´t work anymore, the intellisense, usage resolving etc is good but not THAT good, we are a group of consultants working at a Swedish newspaper and the whole dev department switched to Visual Studio Code yesterday no one could tolerate this anymore nor can any of us understand how this thing is designed, even parsing a gigantic project should not be a problem, adding caching, dirty flags and other tricks... I have no understanding for this behaviour!  

1
Comment actions Permalink

Hello. I'm not an expert in developing IDE but as I know, WebStorm gathers anonymous statistics about user's actions. Maybe this is possible to extract some info about this periodic performance slowdown from all this data as so many users are detecting such problem (me too).

I've used WebStorm for about 9 months and have recently discovered that after couple of hours of IDE usage it starts to perform code analysis extremely slowly. All updates were installed at time

0
Comment actions Permalink

No; the only way to see what's wrong is taking CPU snapshots once the issue occurs.

 

1
Comment actions Permalink

maybe you all just need a new PC, are you running on a crappy PC?  WebStorm isn't meant to run on a slow PC.  A lot of times I hear this it's people with slow ass PCs...then start blaming shit on the tool.

One thing I do do is I disable any plugins that are set to enabled that I don't use.  WebStorm sets plugins when you first install it and a lot of the stuff I don't use such as CoffeeScript support, Jade support stuff like that so keep your plugins list lean meaning uncheck the ones you don't use.

2
Comment actions Permalink

@Dave Schinkel. That was helpful. It was indeed all the various installed and unused plugins that was eating up my CPU. 

Thanks for pointing this out. 

0
Comment actions Permalink

I'm facing the same issues.

 

None of the given directions helped so far.

 

I've disabled as many plugins as possible, but some are critical for my development.

 

Also, that annoying `.gitignore` plugin not working does not help: how can you release a version of the IDE without testing it with the most common plugins first?

 

In any case, I've uploaded my CPU snapshot, which I forgot it was running since yesterday evening. Anyway, I stopped the snapshot when the IDE started hanging.

 

The file is called `PS-181.4445.72_andreasciamanna_12.04.2018_11.36.41.zip` (12.3 mb)

 

the funny thing is that I switched from IntelliJ to PhpStorm because the former was too slow, but I see that was a bad decision :(

0
Comment actions Permalink

@Andrea Sciamanna please create a new thread at https://intellij-support.jetbrains.com/hc/en-us/community/topics/200367219-PhpStorm, or log a support ticket against PHPStorm.

I'm going to close this thread for commenting, it's already a mess

0

Please sign in to leave a comment.