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

VScode WSL Remote open very slowly #11133

Closed
1 of 2 tasks
disloot opened this issue Feb 8, 2024 · 4 comments
Closed
1 of 2 tasks

VScode WSL Remote open very slowly #11133

disloot opened this issue Feb 8, 2024 · 4 comments

Comments

@disloot
Copy link

disloot commented Feb 8, 2024

Windows Version

Microsoft Windows [version 10.0.22621.3085]

WSL Version

2.1.1.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Debian

Other Software

No response

Repro Steps

My WSL Remote opens very slowly and it takes a long time for files to load. I tried disabling the network proxy, but the problem persisted. When I checked the network information in WSL, I found there was a VMware virtual network card inside. I tried uninstalling the virtual network card, and then the problem was resolved. The connection speed became very fast.

Expected Behavior

I want to know if the virtual network card will affect the connection of WSL Remote.

Actual Behavior

after uninstalling the virtual network card, it fixed.
ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 2c:f0:5d:9c:1f:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.3.7/24 brd 192.168.3.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
5: loopback0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:15:5d:16:a4:fd brd ff:ff:ff:ff:ff:ff

Diagnostic Logs

No response

Copy link

github-actions bot commented Feb 8, 2024

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@OneBlue
Copy link
Collaborator

OneBlue commented Feb 13, 2024

@disloot: Can you share /logs of WSL being slow to start ? Do you see this behavior when you start wsl with wsl.exe as well or is this specific to vscode ?

Copy link
Contributor

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants