vscode-remote-release

vscode-remote-release copied to clipboard

• VSCode Version: 1.45.1
• Local OS Version: Win 10
• Remote OS Version: Linux/Ubuntu18
• Remote Extension/Connection Type: Docker & WSL2

Steps to Reproduce:

Editing a large Angular application with ng-serve, locally in 8-core i9 16Gb ram, on save sometimes spikes up load to unusable limits. Last time at 17-load (on that machine) found a top offender (this one)

vscode 63679 3.1 2.1 1289484 43380 ? Sl 04:05 0:14 /home/vscode/.vscode-server/bin/5763d909d5f12fe19f215cbfdd29a91c0fa9208a/node /home/vscode/.vscode-server/bin/5763d909d5f12fe19f215cbfdd29a91c0fa9208a/out/bootstrap-fork --type=extensionHost --uriTransformerPath=/home/vscode/.vscode-server/bin/5763d909d5f12fe19f215cbfdd29a91c0fa9208a/out/vs/server/uriTransformer.js --useHostProxy=

There is a whole list of other spawned all contributing to this load. The same situation repeats itself whether it is WSL2 or Docker.

WSL to I am using the latest insiders build on Win arm64. It is underpowered machine and often i have to use wsl --shutdown and restart as it all just dies.

This is not limited to Angular apps, same behaviour with plain NodeJS and Rust with varied folder structure and complexity

Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: No

Do you actually ask how to monitor and manage resource consumption by NODEJS? This is not a VSCODE topic and the answer can be found in discussions about the deployment configuration of NODEJS applications to the production environment.

@PavelSosin-320 No Pavel, I'm not asking how to manage nodejs resources, I am asking why do the nodejs processes run and orchestrated by vscode in remote dev environment (vscode server) suddenly tend to explode into 20+ load, is it a bug, a missing configuration or resource-related issue i.e. just give it more ram and all will be fine kind of thing. There were similar issues in the past on much older versions of vscode related to having too many files hence the exclusion of /node_modules/* and others.