Webstorm constantly freezes on certain auto-completion actions or imports garbage

I’m very sorry to hear about your bad experience with the IDE.

Could you please share a project where we could reproduce the issues?

I can give one developer access to all my repositories on github. It takes some time to get it installed, since it is composed of a few sub-modules. There is a manual on how to get it to run.

I just tried to create a new project and recreate the issue, but it works fine, so must have something to do with my setup. Please contact me with a github handle.

My github id is lena-spb.

Thank you!

I invited you to all repros. The main one is called “axis” and has a readme.

Thank you!

Unfortunately I'm not sure how to proceed. The very first step (git clone --recurse-submodules) fails with

Cloning into 'axis'...     
remote: Invalid username or password.                                                                                                                           
fatal: Authentication failed for 'https://github.com/andremichelle/axis/'                                                                                                                                                                  

You have to provide your own credentials. Either by using a SSH key or HTTPS + personal-access-token. I double-checked: you have full access to all related repros on my github account.

It was a problem with my access token, it has expired :)

I have successfully cloned the repo, thank you. What steps should I try now to reproduce the issue?

Can you reproduce the steps in the video (WebStorm.freeze.mp4)?

No, unfortunately I failed to reproduce it using similar steps.

The ‘garbage’ imports from the wrong folder do indeed appear. I was able to fix it by un-excluding the dist folders. dist and build folders are auto-excluded as a result of changes introduced in WEB-68312. To get them un-excluded, you can press double Shift, type registry, and open the Registry... window. In this window, disable the exclude.generated.files.in.javascript.package.roots  key, then re-start the IDE.

Unfortunately that does not change it for me. It still auto-imports a lot of garbage.

“exclude.generated.files.in.javascript.package.roots” is still disabled after restarting the IDE.

Also, it still freezes when I create a getter/setter in one go with any private property of the class BlockRenderer.

I've reproduced the ‘garbage imports’ issue. It looks very similar to WEB-65889. Please follow it for the updates.

As for the freezing issue, would it be possible to collect and share log files as the initial troubleshooting step?
These can be collected with the Help > Collect Logs and Diagnostic Data menu action.

Sure: http://www.andremichelle.io/files/webstorm-logs-20250503-17143810722686821904040632.zip

Thank you. It's a thread starvation problem. We have added some fixes in 2025.1.1 update, could you check if it works any better for you after updating?

If it doesn't help, please try the following:

• Add more memory with Help | Change Memory Settings. This doesn't add threads but may cause the IDE to quicker complete the tasks.
• Disable some IDE services which you may tolerate. For example, inspections, inlay hints, gutter icons. This reduces the resource consumption causing having fewer tasks.
• Try toggling Settings | Languages and Frameworks | TypeScript | Enable service-powered type engine. This changes the load balance between IDE and node.

WebStorm 2025.1
Build #WS-251.23774.424, built on April 14, 2025

How do I get 2025.1.1?

Btw: Disabling Enable service-powered type engine seems to fix the freezing issue.

2025.1.1 is not yet published. You can download the preview build here: https://youtrack.jetbrains.com/articles/WEB-A-11/WebStorm-EAP#The-Early-Access-Program-for-the-latest-stable-version-is-currently-closed-Please-check-back-later

Adding to this topic, I'm experiencing the same issues—constant freezing during auto-complete, and sometimes even randomly.

“By the way, disabling Enable service-powered type engine seems to fix the freezing issue.” Mine is already disabled.

I'm already in contact with support regarding this problem, so I won’t go into further detail—just expressing my disappointment with how buggy the 2025 version of WebStorm feels.

Happening to me as well, tried to generate a support ticket. 

Freezes constantly, I can sometimes leave it for a few moments and it will comeback, others and more frequent I quit and start again.

I'm on  a Mac M3 Pro 

Webstorm Build #WS-252.25557.126, built on August 27, 2025

Constantly checking updates. And if I have a .tsx files opened, rarely thank God, CPU goes crazy and fan all the way up.

For me this issue started with 2025.2.2 on Windows

I’m very sorry to hear about your bad experience with the recent IDE version. 

Please try collecting IDE logs after reproducing the issue the IDE logs (these can be collected with the Help > Collect Logs and Diagnostic Data menu action) and share them in a new youtrack ticket so we can investigate your problem more thoroughly.

Elena Pogorelova I have collected the logs using the method you describe, but I'm not at liberty to share all that sensitive information. Is there anything in particular you would need? Then I can see if I can somehow remove sensitive information from there.

We  are mostly interested in the auto-generated thread dumps. They don't include any sensitive information. Also, when attaching logs to the youtrack ticket, you can make them visible to jetbrains-team only to avoid disclosing.

it is happening now with latest version of webstorm. Do you have a fix? this is super annoy. I am thinking moving away from this company

Build #WS-252.26830.93, built on October 1, 2025

WebStorm 2025.2.3
Build #WS-252.26830.93, built on October 1, 2025
Source revision: a4b6b6ae9f201
Licensed to Machool Technologies / Ricky Hai
Subscription is active until October 26, 2025.
Runtime version: 21.0.8+9-b1038.72 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 15.5
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2504M
Cores: 10
Metal Rendering is ON
Registry:
 ide.balloon.shadow.size=0
 ide.new.editor.tabs.vertical.borders=true
 ide.animate.toolwindows=true
 ide.experimental.ui=true
 ide.editor.tab.selection.animation=true
 ide.colorful.toolbar.gradient.radius=600
Non-Bundled Plugins:
 JavaScriptDebugger (252.26830.99)
 com.intellij.tasks (252.26830.102)
 Subversion (252.26830.102)
 ru.adelf.idea.dotenv (252.23892.201)
 com.intellij.ideolog (252.26830.99)
 com.markskelton.one-dark-theme (5.14.1)
 com.godwin.json.parser (1.8.4)
 com.anthropic.code.plugin (0.1.11-beta)
 String Manipulation (9.16.0)
 Docker (252.26830.99)
 org.jetbrains.plugins.gitlab (252.26830.99-IU)
 org.jetbrains.plugins.github (252.26830.99-IU)
 net.seesharpsoft.intellij.plugins.csv (4.1.0)
 com.chrisrm.idea.MaterialThemeUI (10.5.0)
 com.intellij.react (252.26830.99)
 org.jetbrains.plugins.vue (252.26830.102)
 com.github.copilot (1.5.57-243)
 com.mallowigi (103.0.0)
 zielu.gittoolbox (600.1.12+243)
 org.jetbrains.security.package-checker (252.26830.95)
 

Please try collecting IDE logs after reproducing the issue the IDE logs (these can be collected with the Help > Collect Logs and Diagnostic Data menu action) and share them in a new youtrack ticket as suggested above.

I can imagine it is a painful job to ask users to collect data for the developer, but I am tired of spending so much time collecting diagnostics and logs. 

My project is open-source: https://github.com/andremichelle/opendaw. You can simply fork it and reproduce the problems by yourself. If they do not reproduce, you can start comparing my settings and your settings. It is rather time-consuming but quite friendly; we are paying for this.

Webstorm has many features I like, which kept me moving away from IntelliJ products. But the pressure increases every day. There are simply too many bugs. I wish instead of throwing more features at the software, you would prioritise bug fixing for a year.

I'm following this post... I've noticed some improvement in WebStorm since version 2025.2.3, but only when working on backend applications (I'm using NestJS, not sure if that's related).

However, it's still painfully slow for Next.js when developing frontend apps, everything freezes, and autocomplete is incredibly sluggish

I often have 2, 3, or even 4 WebStorm instances open at the same time, and it only freezes on the Next.js project window. It's pretty clear the issue gets worse when dealing with .tsx files

I'll probably rollback to 2024 versions, never got any issue at those versions