-
Notifications
You must be signed in to change notification settings - Fork 798
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
WSL2: wsl.exe hangs for 10s of minutes before working #11067
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:
|
My
And just to provide as much helpful information as I can, I'm going to create yet another WSL log right before I restart: It might help to show the times in which I created these logs: re: the bot's linksAs far as I can tell those issues weren't exactly the same as mine. This one appears to have the most helpful information, mainly the second half of the comments: #4144 I use the word "appears" because I tried one and it didn't fix the problem: I looked into my After I killed it, I opened a new wsltty terminal and it's hanging like before. I don't plan to stick around long enough to see if it eventually finishes; I'm going to restart my computer now. |
I tried the other major suggestion from #4144
It did not fix the issue. I ran |
Okay I decided to Everything was working fine with my new install. Then, I these last two steps, then the permanent hanging issue immediately came back: 1.I modified my 2.
It was this: PS C:\Windows\system32> wsl --version It became this: PS C:\Windows\system32> wsl --version Now I'm stuck at WslLogs-2024-01-24_23-28-12.zip It might be worth noting vmmem is running in the task manager again. Without reinstalling WSL, I killed WSL in the task manager, unregistered my imported distro, reimported it, set the user to the original value. I'll report back if it happens yet again. If it does happen again, next I'll try reinstalling WSL without running It seemed to be working all right until I noticed vmmem was using 1.5 gigs, so I ran Guess I'll reinstall everything from scratch again. |
okay I followed these steps again but skipped the So far so good. Up to this point I could reproduce these problems in one tenth of the time and in one tenth of the attempts to trigger it. I'm willing to run |
/dumps |
@OneBlue I've attached six log files throughout this thread. You can find them by searching for ".zip" in your browser. Let me know if they are missing information. Thanks |
@OneBlue Hope you don't mind the second ping so soon. Let me know how else I can help, because I think I'm in a good position to do so! |
@DanKaplanSES: I'm not seeing any dumps in the zip files, I think given that the symptoms what we need is a dump of the WSL processes while things are 'stuck'. /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.3930]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
I can't run wsl.exe --status right now because wsl is hanging
Distro Version
I can't run lsb_release -r right now because wsl is hanging
Other Software
wsltty, updated earlier today while experiencing this problem: https://github.com/mintty/wsltty/releases/tag/3.7.0.2
Repro Steps
Unfortunately I can't reproduce this consistently. After a fresh restart, wsl.exe / Ubuntu usually behave as expected, but after hours of uptime, wsl.exe hangs.
Normally I don't wait for it to finish: it can take up to 30 minutes before a wsl.exe command completes, and it doesn't always result in resolving the problem when it does complete. Sometimes it errors, sometimes wsl.exe starts an ubuntu prompt.
Expected Behavior
I would like wsl.exe to immediately respond with correct output. e.g., if I run
wsl.exe --status
, I would like to immediately see that response.If wsl.exe can't be run for some reason, I would like it to fail fast instead of 30 minutes later. I've been waiting 20+ minutes for
wsl.exe --status
to complete as I write this up, but I will probably restart my computer before it finishes because it is blocking my ability to work.Actual Behavior
Occasionally, any
wsl.exe
command will hang for 10s of minutes before showing any output.Diagnostic Logs
WslLogs-2024-01-23_15-16-07.zip These first logs prompted me to create this issue. I ran
wsl
in an administrator cmd.exe and it took a very long time to complete. I captured the log while it was hanging and then noticed it completed. This seemed unique enough to share, as I haven't noticed other issues saying it worked eventually after waiting long enough: it opened up a wsl command prompt (2nd line of screenshot).The first line occurred after I manually killed the wsl service in the task manager (shown in this screenshot) then ran
wsl
:Eventually it errored with
Server execution failed\nError code: Wsl/0x80080005
. I tried again and it hung for 10+ minutes, but then it opened up the wsl command prompt. All of the other commands worked immediately except for the very last line (i.e.,wsl.exe --status
). I'm still waiting on that one and it feels like it's been ~45 minutes at this point.WslLogs-2024-01-23_15-28-12.zip The second logs were generated when I ran
wsl.exe --status
and it was hanging 1-20 minutes when I collected those logs (sorry I'm not timing it exactly).Just in case it may help, WslLogs-2024-01-23_16-04-16.zip these logs are of the same hanging
wsl.exe --status
command. This one is around 20-45 minutes since it started.wsl.exe --version
:I'm not sure if this should be running in the latest WSL2 versions, but whenever these symptoms occur, I've noticed that the
vmmem
process is no longer running in the task manager.I'm sure there's way too much information in here as it is, but I decided to thoroughly document a similar troubleshooting experience I had a few weeks ago. Perhaps it'll provide some useful information: https://superuser.com/questions/1825580/how-do-i-troubleshoot-an-unresponsive-wsl2-on-windows-10
After system restart 1 of n
wsl
was working fine for ~20 minutes, but now everything is hanging like before. Here's a fresh log:WslLogs-2024-01-23_17-56-57.zip
After system restart 2 of n
I can get some of this information now.
Kernel Version
Distro Version
The text was updated successfully, but these errors were encountered: