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 does not respond after some time #12045

Closed
1 of 2 tasks
ThePlenkov opened this issue Sep 17, 2024 · 8 comments
Closed
1 of 2 tasks

WSL does not respond after some time #12045

ThePlenkov opened this issue Sep 17, 2024 · 8 comments

Comments

@ThePlenkov
Copy link

Windows Version

Microsoft Windows [Version 10.0.22631.4037]

WSL Version

2.3.21.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu

Other Software

No response

Repro Steps

I'm just typing wsl and that's it - it's hanging and not responding. Restart helps to solve the issue.

Expected Behavior

It should not hang and respond quickly

Actual Behavior

It hangs and not responding, it is not possible to start, shutdown or terminate wsl

Diagnostic Logs

No response

Copy link

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 wsl-gh-logs@microsoft.com 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'.

View similar issues

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!

Open similar issues:

Closed similar issues:

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

@ThePlenkov
Copy link
Author

well in my case it is not related to hibernate 100%. Right now I was just typing something in the console when it got stuck just during typing.. It's totally blocking my work cause the project is set up in WSL..

@OneBlue
Copy link
Collaborator

OneBlue commented Sep 17, 2024

/dumps

@ThePlenkov
Copy link
Author

File size too big: 25 MB are allowed, 362 MB were attempted to upload.

@ThePlenkov
Copy link
Author

ThePlenkov commented Sep 18, 2024

what I noticed - when I stop Docker Desktop - the issue is not appearing..

@ThePlenkov
Copy link
Author

Look - i just found the actual reason! It was because of the docker resource saving mode! Once I go to DOcker desktop and press the play button - WSL alives immediately! How to communicate now to WSL team or may be even Docker?? It seems like issue needs investigation.

@ThePlenkov
Copy link
Author

And here it is: #11066 exactly what I have

@ThePlenkov
Copy link
Author

the workaround is to set autoMemoryReclaim=dropcache instead of gradual

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

No branches or pull requests

2 participants