vscode: High CPU consumption when idle

Does this issue occur when all extensions are disabled?: No (it does not happen when running VSCode in Windows, does happen in WSL) - no other extension than Remote - WSL is enabled/installed

VS Code Version: Version: 1.61.0-insider (system setup) Commit: f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78 Date: 2021-09-14T05:15:56.612Z Electron: 13.1.8 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19043
OS Version: using WSL1 on Win 10 x64 Enterprise Edition and running VSCode remotely in WSL OS: Ubuntu 18.04.2 LTS on Windows 10 x86_64 Kernel: 4.4.0-19041-Microsoft

Steps to Reproduce:

start VSCode Insiders and wait until everything is up
run ps -eo pcpu,pid,user,args
observe high CPU usage:

eip@LAPTOP-O4GG982K:~$ ps -eo pcpu,pid,user,args
%CPU   PID USER     COMMAND
 0.0     1 root     /init
 0.0  1547 root     /init
 0.0  1548 eip      -bash
 0.0 14916 root     /init
 0.0 14917 eip      sh -c "$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78 insider .vscode-server-insiders 0  
 0.0 14918 eip      sh /c/Users/PeterKrokavec/.vscode-insiders/extensions/ms-vscode-remote.remote-wsl-0.58.2/scripts/wslServer.sh f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78 insider .vscode-server-insiders 0
 0.0 14924 eip      sh /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/server.sh  --port=0 --use-host-proxy --without-browser-env-var --disable-websocket-compression --print-ip-address --enable-remote-auto-shutdown
13.3 14926 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/vs/server/main.js  --port=0 --use-host-proxy --without-browser-env-var --disable-websocket-compression --print-ip-address --enable-remote-auto-shutdown
 0.0 14937 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/bootstrap-fork --type=ptyHost
 0.7 14974 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/bootstrap-fork --type=watcherService
52.5 15197 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/bootstrap-fork --type=extensionHost --uriTransformerPath=/home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/vs/server/uriTransformer.js --useHostProxy=
 0.0 25235 eip      ps -eo pcpu,pid,user,args

I haven’t noticed this last week, but today I upgraded VSCode to latest version (I was prompted that there was a new version to install so I did although I was already on 1.61.0-insiders since the last week)

Is there a possibility to downgrade my insiders build to an older one?

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 1
Comments: 18 (7 by maintainers)

Most upvoted comments

Possibly related to #136509 @krokyk are you still seeing the issue on the latest Stable? (v1.63)

rzhao271 on Dec 15, 2021

Not sure if my problem is the same or just similar.

I’m using vscode on windows and connect, via Remote - SSH, to an ec2 instance (running linux).

If no other extension is installed (either local or remote), all is good.

If I try to use the ms-python extension (installed on the remote), I get one of the cores of my ec2 instance maxed out (and it looks like it jumps from one core to the other) by the “bootstrap-fork --type=extenionsHost” node process. This in turn makes the vscode client disconnect from the remote host (I get lots of “[renderer1] [error] read ECONNRESET: Error: read ECONNRESET” in the Log - Window log window) and this in turn makes things like creating new files, deleting new files, searching folders etc unbereable long (create and delete eventually end, but I never had the patience to wait for a search). Additionally, if I close down vscode, the vscode-server does not shut off and keeps hogging resources (to the extent that my app cannot run on the server).

This started happening about 2 days ago or so.

coditza on Sep 22, 2021