1 CPU: Visual Studio Code 100% CPU and System freeze on startup win 7 64 bit

[ParikshitBhagawati]

I have a windows 7 64bit PC running on an AMD processor with on board NVIDIA graphics chipset and 8 gb of RAM. I have tried various versions of vs code but the result is the same. It freezes the system for about 2 minutes until it opens it with a 100% CPU usage.

I have also tried different options like disable GPU and running without extentions etc. but all in vain.

I have an older laptop with 1gig RAM and windows 7 32 bit where vs code 1.1 runs without any of the above issues smoothly.

Can you please help ?

• VSCode Version: 1.1 tot 1.16
• OS Version: Windows 7 Ultimate 64bit

Steps to Reproduce:

1. Open visual studio code
2. System freeze and 100% CPU

Reproduces without extensions: Yes

[alexdima]

@ParikshitBhagawati VS Code uses multiple processes. Maybe it could help us figure out what's going on if we could find out which process is using 100% CPU. You can use a tool like process explorer and hover over the process that is at 100% CPU so we can find out the arguments it is launched with (i.e. identify which of our processes it is)

[ParikshitBhagawati]

@alexandrudima thanks for your response. attached is the screenshot from process explorer. please let me know if this help you with the info you were looking for.
p.s - using the insiders build now.

[ParikshitBhagawati]

Here's more from today!

[alexdima]

I haven't seen so far our main process going crazy like this.

[bpasero]

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

[ParikshitBhagawati]

Well, the profile sent before was with the insiders build (Version 1.17.0). The link you provided however takes me to the download page for the latest stable build I guess, which is 1.16.1. But I downloaded it anyway with no change in results (100% CPU, unresponsive system etc.) and took 10 minutes to open.

Attached is the profile snapshot with the latest build.

Thanks!

[bpasero]

@ParikshitBhagawati is this a single CPU VM?

[ParikshitBhagawati]

Its not a VM.. It's a native single core processor.

[bpasero]

Yeah. VS Code does not run well on 1-CPU systems. This is a known issue that was reported before.

[ParikshitBhagawati]

So is there a fix /work around for this yet or planned in the future ? Or it just wont work ?

[vaibhavsingh97]

I also facing same issue. After launching visual studio, RAM become 100% and my desktop freezes
OS: Arch Linux
Kernel: 4.13.4-1-ARCH

[ahumeniy]

In Windows you can launch VS Code with low or below normal CPU priority and it won't freeze your machine. If you're already affected you can open task manager and set the priority for the processes using 100% CPU to either low or below normal priority. After a while the high CPU usage will stop.

[royBrocken]

I changed my win7 VM to use multiple processors, and vscode is running fine again.

[lbertolotti]

My system is not freezing, but it almost did.

• VS code version 1.9.1 Architecture x64
• OS version: Windows 10 Home
• Processor: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz 2.40 GHz
• Installed memory(RAM): 4.00 GB (3.89 GB usable)
• System type: 64-bit Operating System, x64-base processor
• memtest 86+ no errors found.

[ParikshitBhagawati]

As mentioned by @bpasero VS code doesn’t work well with single core CPUs. I had an option to enable multiple cores for my processor and when I did, Code started to work fine without the system freeze / 100% CPU issue.

[TBubba]

I had the same issue on my garbage single core CPU laptop, but changing the priority of the process to "Below Normal" makes it work fine. Now it's at 0% usage most of the time and goes up to ~10% when the window re-renders. Thanks y'all!

(In my case, setting the priority to "Low" made it a little bit more responsive than "Normal" but it still used 100% CPU)

[3dfoster]

@bpasero I am having the same issue on an AMD Ryzen 1300x (four physical cores) so I don't think it is a single core issue.

[ignite-404]

same here

[JohnProg]

same here

[jmbuhr]

same issue on Win 10, with code and code-exploration. Also code doesn't open without internet connection

[LydiaMennes]

same here, it makes the IDE almost unusable

[r4hulCorleone]

I had same problem with newest update ,1 physical core ,100 cpu usage,window 7
[Solution]:change compability mode to windows xp sp3 for vs code solved my problem.

[ergenekonyigit]

same problem here.

• macOS 10.14.1
• code 1.29.1

[KristofStroobants]

Same problem here. I reverted back to 1.25
Seems like that is the latest usable version for me.
Is there any update on a fix ????

[gustaff-weldon]

Experiencing the same issue. CodeHelper is stuck on ~100%.

ps aux output on that process:

✗ ps aux | grep 13158
-edited-    13158  99.5  1.4  6194332 242864   ??  R    Tue09AM  59:28.99 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /var/folders/5b/gz8j6f890kb2pd1n6zfn09c00000gn/T/vscode-typescript/tscancellation-87c31d99c306e6ae821e.tmp* --locale en --noGetErrOnBackgroundUpdate

Looks like Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js is a culprint. My project is a monorepo with a lot of JS code (not TS enabled)

OSX 10.13.6
Code 1.29.1 (1.29.1)

[kyegupov]

same issue (Linux - Xubuntu 18.10, vscode 1.29.1)

[lautis0503]

This could be a bug from electron. There's a bug fix finally.
electron/electron#15975

[bpasero]

I finished a build with the fix from electron/electron#15975:

https://az764295.vo.msecnd.net/insider/5967828c2a5c559ed86c3369ed9811bb1bd6386b/VSCode-win32-x64-1.31.0-insider.zip

Can people report back if this is fixed with that build?

[9chu]

I finished a build with the fix from electron/electron#15975:

https://az764295.vo.msecnd.net/insider/5967828c2a5c559ed86c3369ed9811bb1bd6386b/VSCode-win32-x64-1.31.0-insider.zip

Can people report back if this is fixed with that build?

Solved on my VPS with 1 core CPU, running Windows Server 2012 R2.

[pkathro]

I finished a build with the fix from electron/electron#15975:

https://az764295.vo.msecnd.net/insider/5967828c2a5c559ed86c3369ed9811bb1bd6386b/VSCode-win32-x64-1.31.0-insider.zip

Can people report back if this is fixed with that build?

This build fixed the issue for me.
Tested on 2 x single core VMs running Win 2008 and 2008 R2 respectively

[bpasero]

Very cool, thanks for confirming!

[bpasero]

Closing this issue given that we plan to release VSCode stable early February with Electron 3.x. If you want to benefit from the fix already, consider to use our insiders version that already contains the fix: https://code.visualstudio.com/insiders/

[KristofStroobants]

Insider or not; electron 3 or not, VS Code takes minutes to just open up.
My only good working version is v1.25. Anything above that is so slow that it becomes unusable at this point. There are so many people mentioning this but i haven't read about a fix. Yeah you can have a look into the processes but that gives you numbers we don't even understand. I really wish you guys either came out with a fix OR with some better way for us to help finding out what is causing this.

[viniciusgati]

I finished a build with the fix from electron/electron#15975:
https://az764295.vo.msecnd.net/insider/5967828c2a5c559ed86c3369ed9811bb1bd6386b/VSCode-win32-x64-1.31.0-insider.zip
Can people report back if this is fixed with that build?

This build fixed the issue for me.
Tested on 2 x single core VMs running Win 2008 and 2008 R2 respectively

Me to.

[ssj7]

I have a core i7 and it still takes about 10 sec to open an ionic project. I have 16GB ram.
Version: 1.31.1 (user setup)
Commit: 1b8e830
Date: 2019-02-12T02:20:54.427Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 6.3.9600