WebStorm 2017.3.4 freezing temporarily then working again

I'm running Windows 10 and I was using WebStorm 2017.3.4, working on TypeScript and Node.js projects.

I'm was having exactly the issue described here:

https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000132704-WebStorm-2017-1-Hanging

Sometimes in the middle of typing, navigating, or doing other tasks, WebStorm would freeze for around 30 seconds. Then it starts working again. It did this around once every 5-10 minutes. I couldn't see any kind of indexing or other special activity going on at this time. Sometimes I'd just type a character and boom.

During this period, WebStorm would have its CPU extremely high but the memory didn't change much. It happened on tiny projects and bigger ones.

It didn't happen right after an upgrade, I've been using 3.4 since it came out. So it's pretty weird.

I'm the kind of person who tries everything else before going to support, so I tried a bunch of things:

1. Turning off various programs running in the background
2. Cleaning cache and restarting WebStorm
3. Restarting the computer
4. Deleting WebStorm folders in AppData and `.WebStorm`, thne importing my preferences back.
5. Deleting workspace `.idea` folder.
6. Deleting all WebStorm folders without importing my preferences, just in case.
7. Uninstalling WebStorm and reinstalling
8. Uninstalling CLion that I also had.

In the end, nothing could get it fixed. As a last-ditch attempt I uninstalled WebStorm and installed the previous semi-major release (2017.2.5), and this successfuly solved my problem somehow, even though the issue has only been going on since the start of today and I've been using 3.4 for ages.

This solution doesn't seem to make sense. I think there must be some other WebStorm settings that I didn't delete, and those caused the issue, since I could see WebStorm still knew it was still installed in the past when I reinstalled it. Maybe switching to another version doesn't use the same settings.

Since I have my development environment working, I'm probably not going to go out of my way debugging this, but I thought you could use the bug report and maybe someone could use my workaround. If there's anything I can do to get the newer version running again, please tell me.