-
Notifications
You must be signed in to change notification settings - Fork 823
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
WSL freezes #11232
Comments
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! Open similar issues:
Closed similar issues:
|
/dumps |
@OneBlue I attached the output from |
@andreasWallner: What we need is a dump of the WSL processes, which you can get by adding For some reason the bot didn't trigger, but it should give the exact command for that. /dumps |
Hello! Could you please provide logs and process dumps to help us better diagnose your issue? To collect WSL logs and dumps, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 Thank you! |
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! |
Windows Version
Microsoft Windows [Version 10.0.19045.4046]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Expected Behavior
WSL should continue working like before the sleep/disconnect
Actual Behavior
vmem
uses >80% CPUwsl --shutdown
hangswslservice.exe
needs to be killed manually to restore functionalityDiagnostic Logs
WslLogs-2024-03-01_09-42-28.zip
The text was updated successfully, but these errors were encountered: