Skip to content

High cpu usage of node process in Remote-WSL extension #2921

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dingqunfei opened this issue May 3, 2020 · 6 comments
Closed

High cpu usage of node process in Remote-WSL extension #2921

dingqunfei opened this issue May 3, 2020 · 6 comments

Comments

@dingqunfei
Copy link

  • VSCode Version: 1.44.2
  • Local OS Version: Windows_NT x64 10.0.18363
  • Remote OS Version: WSL Ubuntu 20.04
  • Remote Extension/Connection Type: Remote-WSL v0.44.2

Steps to Reproduce:

  1. I code or debug in WSL, following this https://code.visualstudio.com/docs/cpp/config-wsl.
  2. Step by Step following the tutorial, after installed the remote-wsl , the node process has a high cpu occupation forever.
  3. I disabled the extension one by one. When Remote-WSL extension is disabled, the CPU usage is low. Does this extension cause high occupation? I just code or debug in VSCode by WSL, and the Remote-WSL helps me to use gcc/gdb in WSL. By the way, this is no database icon or flame in the status bar.

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
微信图片编辑_20200502005044
微信图片编辑_20200502005121

@csibesz07
Copy link

csibesz07 commented May 3, 2020

  • VSCode Version: 1.44.2 (user setup)
  • Local OS Version: Windows_NT x64 10.0.18363.778, Windows 10 Pro N
  • Remote OS Version: WSL Ubuntu 20.04
  • Remote Extension/Connection Type: Remote-WSL v0.44.2

I see the same issue. I have the same versions as reporter.
Just reinstalled windows 10, everything the latest.
I have 2 WSL VSCode window open, both using one core fully (99, 98). Some kind of livelock.
Tried to revert back to VSCode 1.35, same there. Should try to older ubuntu version and see if it makes difference.
wsl_cpu_usage
EDIT:
Installed WSL Ubuntu 18.04 and no absurd CPU usage there. So this is a quick workaround.

@dingqunfei
Copy link
Author

YES, Phenomenon appears after upgraded to WSL-Ubuntu20.04

@Manntis
Copy link

Manntis commented May 5, 2020

Agreed. @csibesz07 downgrading VSCode WSL to Ubuntu 18.04 resolved the issue for me as well. I tried all of the file watching related fixes with no luck. (#90)

@emeygret
Copy link

emeygret commented May 6, 2020

probably due to this : https://discourse.ubuntu.com/t/ubuntu-20-04-and-wsl-1/15291
and this : #864

@emeygret
Copy link

emeygret commented May 6, 2020

solve with patched libc6 :
wget "https://launchpadlibrarian.net/474302949/libc6_2.31-0ubuntu8+lp1871129~1_amd64.deb"
sudo dpkg -i libc6_2.31-0ubuntu8+lp1871129~1_amd64.deb

no issue with wsl2, and issue seems to be fixed in wsl1 in next version

more information in microsoft/WSL#4898

@frct1
Copy link

frct1 commented May 10, 2020

solve with patched libc6 :
wget "https://launchpadlibrarian.net/474302949/libc6_2.31-0ubuntu8+lp1871129~1_amd64.deb"
sudo dpkg -i libc6_2.31-0ubuntu8+lp1871129~1_amd64.deb

no issue with wsl2, and issue seems to be fixed in wsl1 in next version

more information in microsoft/WSL#4898

Hey, it seems to be working. Thank you very much!

@github-actions github-actions bot locked and limited conversation to collaborators Jun 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants