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

WSL freezes #11232

Closed
1 of 2 tasks
andreasWallner opened this issue Mar 1, 2024 · 6 comments
Closed
1 of 2 tasks

WSL freezes #11232

andreasWallner opened this issue Mar 1, 2024 · 6 comments

Comments

@andreasWallner
Copy link

Windows Version

Microsoft Windows [Version 10.0.19045.4046]

WSL Version

1.2.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

  • Run Ubuntu after reboot
  • disconnect docking station, send computer to sleep/hibernate
  • wake up machine, reconnect docking station

Expected Behavior

WSL should continue working like before the sleep/disconnect

Actual Behavior

  • WSL is frozen, terminal does not react anymore
  • vmem uses >80% CPU
  • wsl --shutdown hangs
  • wslservice.exe needs to be killed manually to restore functionality

Diagnostic Logs

WslLogs-2024-03-01_09-42-28.zip

Copy link

github-actions bot commented Mar 1, 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!

Open similar issues:

Closed similar issues:

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

@OneBlue
Copy link
Collaborator

OneBlue commented Mar 4, 2024

/dumps

@andreasWallner
Copy link
Author

@OneBlue I attached the output from collect-wsl-logs.ps1 the to OP, from exactly those commands. Is something wrong with them?

@OneBlue
Copy link
Collaborator

OneBlue commented Apr 18, 2024

@andreasWallner: What we need is a dump of the WSL processes, which you can get by adding -Dump to collect-wsl-logs.ps.

For some reason the bot didn't trigger, but it should give the exact command for that.

/dumps

Copy link
Contributor

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:

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 -Dump

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!

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