Freezing on require() when code completing on package names
When doing a require() in WebStorm to import a package from my node_modules directory, after I type the first character WebStorm freezes. This only happens when I'm running WebStorm on Windows, when running on Mac this does not happen. I've been trying to resolve this problem for the past few versions, I'm currently running WebStorm 2017.2.1 on Windows 7 64-Bit.
I've also looked into the log directory at noticed that when this happens (which is on every single require) a new directory called "threadDumps-freeze-<date>-WS-172.3544.34-<duration>sec. Where date is the YYYYMMDD formatted date on which WebStorm froze and duration is the length of the freeze. Within that a file named threadDump-20170808-123132.txt is created with around 600 lines of Java StackTraces. I've uploaded the log file to the JetBrains Support Attachments
This problem is making WebStorm unusable for development as it freezes every time I go to use a package, if there is anymore info needed let me know.
Please sign in to leave a comment.
sorry, but I have no idea where to look for JetBrains Support Attachments. Please can you upload thread dumps to ftp://ftp.intellij.net/.uploads/ and let me know the file names?
I uploaded one of the thread dumps to the FTP with the name threadDump-20170808-123132.txt
Also I originally uploaded that file to https://uploads.services.jetbrains.com/
dump shows that it's busy loading some image via ftp(?)
please can you upload other thread dumps plus idea.log?
I uploaded all the thread dumps from this instances and the idea log in a ZIP called peteb-WS idealog and freeze dumps
Also, I have no FTP setup or anything like with my WebStorm to the best of my knowledge. Is there a place I could check for a setup on FTP. Doing a search in Settings for "FTP" yielded nothing.
thanks - still the same: all dumps show issues loading icons through inet connection...
as far as I can see, you are using a custom theme - Afterglow Theme plugin. Please try disabling it - does the issue persist?
Looks like that did the trick. I disabled the Afterglow Theme plugin (also uninstalled it) and did the trick it seems.
Thank you for all the help Elena.
Great, thanks for update:)