microsoft / microsoft/WSL

Network crashed after using VSCode WSL plugin connected to container

Open
#40,490 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

emailed-logs
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

### Windows Version

Microsoft Windows [Version 10.0.26200.8246]

### WSL Version

2.7.1.0

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

6.6.114.1-1

### Distro Version

Ubuntu-24.04

### Other Software

Visual Studio Code 1.119.0 with WSL plugin 0.104.3

### Repro Steps

1. Connect to WSL with VSCode WSL

### Expected Behavior

Nothing should happend.

### Actual Behavior

Network become extremly slow both on host and inside WSL, packet lossing rate and latency increase significantly when pinging gateway of my home network, at this stage it's recoverable by executing `wsl --shutdown`.
If ignoring this situation, after a few minutes, network card will stop working, the WLAN icon disappear from notification area, any attempts try to adjust network settings, include Settings App of Windows, quick network settings in notification area, will result a hang of the app or explorer.exe, can't poweroff or restarting system, Windows will stuck at "Restarting" or "Shutting down", only can recover by performance a hard power reset by long pressing power button.

### Diagnostic Logs

_Not collected yet, I need to submit this issue first. I had to performace a hard reset after I try to reproduce this issue_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with WSL 2.7.1.0, Ubuntu-24.04, Visual Studio Code 1.119.0, and WSL plugin 0.104.3. Collect the diagnostic logs that are currently missing and compare the network behavior before and after connecting; done requires identifying the cause of the host and WSL network failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, ubuntu, vscode
Domain
networking, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.