WSL icon indicating copy to clipboard operation
WSL copied to clipboard

WSL hangs randomly

Open zack6849 opened this issue 9 months ago • 7 comments

Windows Version

Microsoft Windows [Version 10.0.26120.3863]

WSL Version

2.5.6.0

Are you using WSL 1 or WSL 2?

  • [x] WSL 2
  • [ ] WSL 1

Kernel Version

6.6.84.1-microsoft-standard-WSL2

Distro Version

Ubuntu 24.04.2 LTS

Other Software

No response

Repro Steps

Run WSL for a while? unclear steps, seems intermittent.

Expected Behavior

WSL is responsive

Actual Behavior

WSL becomes totally unresponsive at random, existing WSL terminal instances do not respond, eg: typing letters doesn't show in the terminal, new ones will spawn a windows terminal window with a blank screen and no prompt, and even commands like wsl.exe --shutdown hang for over a minute before executing

Diagnostic Logs

Will be emailed

zack6849 avatar Apr 16 '25 14:04 zack6849

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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 and reply with '/emailed-logs'.

github-actions[bot] avatar Apr 16 '25 14:04 github-actions[bot]

/emailed-logs

zack6849 avatar Apr 16 '25 14:04 zack6849

Diagnostic information
Found '/emailed-logs', adding tag 'emailed-logs'

github-actions[bot] avatar Apr 16 '25 14:04 github-actions[bot]

Also related feedback hub report from last week with the same issue that also has logs attached hopefully that may help https://aka.ms/AAvo0bc

zack6849 avatar Apr 16 '25 14:04 zack6849

Hi guys, has anyone taken a look at this? i get things aren't always fast / take time to debug, but i hadn't heard a peep, should I continue trying to collect logs of this if the ones i sent above didn't have anything useful in them? It's not 100% of the time and has been less of a nuisance lately, but it is a frustrating bug to deal with.

zack6849 avatar Apr 23 '25 23:04 zack6849

I'm also now seeing an interaction with docker desktop, it enters "resource saver mode" and makes my main WSL instance stop responding, if I hit resume it seems to unfreeze it, I'm not sure if this is another component of the original issue, or a new issue.

zack6849 avatar May 12 '25 14:05 zack6849

I'm seeing the same behaviour, WSL freezes when Docker Desktop enters Resource Saver mode and "unfreezes" when it leaves.

WSL version: 2.5.7.0 Kernel version: 6.6.87.1-1

Docker Desktop Version: 4.41.2 (191736)

johanhammar avatar Jun 02 '25 05:06 johanhammar

I am having this problem: WSL version: 2.5.9.0 Kernel version: 6.6.87.2-1 WSLg version: 1.0.66 MSRDC version: 1.2.6074 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.4061

mpEsri avatar Jul 01 '25 20:07 mpEsri