Freeze after last update

 Hello.

I and my colleagues are using Webstorm but after last update its became totally unusable: its freezing every 10 seconds and sometimes reports "not enough memory".

We have found a workaround: in power safe mode everything works fine

I have upload logs by yours webform with the filename "uguyshaveaverystrangewaytoattachlogs.zip"

Please help.

 

WebStorm 2016.2.3
Build #WS-162.1812.21, built on September 4, 2016
Licensed to Yandex LLC

JRE: 1.8.0_112-release-b343 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

 

 

11 comments

Please provide memory snapshots created when WebStorm runs out of memory. Auto-created memory dumps are saved to a file called 'java_pid <pid> .hprof' in your home or in the working directory of the VM. If you can't locate these files, you can specify an alternative file name or directory with the -XX:HeapDumpPath= option (should be added to .vmoptions file - see https://intellij-support.jetbrains.com/hc/en-us/articles/206544869) - WebStorm will save .hprof files to the specified path next time it runs out of memory

0

Thank you for your response.

I've uploaded file with name "heapDump-Webstorm-1473684651840.hprof.zip " to uploads.jetbrains.com

(or you can take it here https://yadi.sk/d/CeYa3lzCv4qao  )

0

Unfortunately the dump shows that only 84MB are used. It sometimes happens that auto-created memory dumps are slightly delayed and captured after memory was cleared. Could you please capture CPU snapshot instead? See https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems for instructions

0

Sorry for the late answer.

I've uploaded CPU snapshots to uploads.services.jetbrains.com 

WS-162.1812.21_asolomentsev_15.09.2016_10.57.07.zip (8 mb)  (alt: https://yadi.sk/d/QT9_n8pzvBiRJ)
WS-162.1812.21_asolomentsev_15.09.2016_11.19.29.zip (5.9 mb) (alt: https://yadi.sk/d/7cYOQuaBvBiTU)
 
I'm waiting for your response. Thank you.
0

Hello.

Any news? 

I still cant work in ws properly.

0

How big is your project?
The issue is related to having hundreds of same-named elements in the project (https://youtrack.jetbrains.com/issue/WEB-18670). As a workaround, please try excluding node_modules folder, along with all folders generated dynamically by build process (if any) from indexing (Mark directory as/Excluded) - does it make things any better?

0

Thanks for your response!

Project not so big, about 150MB and node_modules 300MB.

But it has some symlinks

core/

mobile/

   node_modules/

       core -> ../../core

desktop/

   node_modules/

       core -> ../../core

 

And its quite strange what performance was normal till last update

 

0

symlinks, especially recursive, may be the issue...

0

SO, what else can i do to help you investigate the problem?

0

Hello!

Do you have any news about this issue?

0

Please sign in to leave a comment.