Skip to content
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

uriTransformer.js consume 100% CPU in WSL #2353

Open
libbkmz opened this issue Feb 13, 2020 · 9 comments
Open

uriTransformer.js consume 100% CPU in WSL #2353

libbkmz opened this issue Feb 13, 2020 · 9 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug performance
Milestone

Comments

@libbkmz
Copy link

libbkmz commented Feb 13, 2020

Version: 1.43.0-insider (system setup)
Commit: 1fbacccbc900bb59ba8a8f26a4128d48a1c97842
Date: 2020-02-13T06:41:13.411Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

  • VSCode Version:1.43.0-insider (system setup)
  • Local OS Version: Windows_NT x64 10.0.18363
  • Remote OS Version: ArchLinux
  • Remote Extension/Connection Type: WSL

This issue is also occures in 1.42 release. on 1.41 wasn't

Steps to Reproduce:

  1. Install VS Code Insiders build
  2. Install Remote WSL
  3. run code . from wsl from empty folder

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, only with WSL extension

@aeschli
Copy link
Contributor

aeschli commented Feb 17, 2020

Does the remote window open?
Can you open Help > Process Explorer and send a screenshot?

It could be an extension that blocks. To find that out you need to disable all the remote exensions.

  • Open the extensions viewlet
  • In the WSL: Ubuntu - Installed section, select and disable the extensions and reload

@libbkmz
Copy link
Author

libbkmz commented Feb 17, 2020

Here is the screenshot of process explorer: image

Ahh, I think this issue is related to this: microsoft/WSL#4898
And I think it's not related to the new version of the VS Code or WSL-Remote extension...
What do you think?

@libbkmz
Copy link
Author

libbkmz commented Feb 17, 2020

I have downgraded glibc in Archlinux to 2.30.3 and this seems to solve the problem.

@aeschli
Copy link
Contributor

aeschli commented Feb 17, 2020

I haven't run VSCode Remote on a WSL-ArchLinux distro yet.
How did you get/create that WSL distro?

@libbkmz
Copy link
Author

libbkmz commented Feb 17, 2020

I've used zip archive from this: https://github.com/yuk7/ArchWSL

@wan230114
Copy link

I also encountered the same problem

@tysonite
Copy link

I've found the same with SSH: #3857

@marcoaleixo
Copy link

This still happening to me.

image

@danjdewhurst
Copy link

Happening to me on Windows 10, WSL Ubuntu 21.04.

@aeschli aeschli added performance bug Issue identified by VS Code Team member as probable bug labels Dec 15, 2022
@aeschli aeschli added this to the Backlog milestone Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug performance
Projects
None yet
Development

No branches or pull requests

6 participants