WSL is non-responsive after waking from hibernate #8696
Comments
|
|
|
|
|
WslLogs-2022-08-08_08-43-05.zip logs captured while trying to restart wsl |
|
WSL has found it hard to reconnect to the PC's storage by the sounds of things. The next time this happens, I believe restarting WSL will fix it, as it does appear to have a memory leak as well. Close then re-open is what I meant by this. |
|
But how do I restart wsl? wsl --shutdown just hangs. |
|
You close it. Then you re-open it. |
|
If it won't close, open task manager then kill the process from there. |
|
Same happens to me, no posible to |
|
Hello Edit : I managed to relaunch it without restarting windows by killing all wsl processes in task manager |
|
I don't think this is related to hibernation, I was also using PHPStorm (latest version which was supposed to have fixed a bug with WSL). I have finally abandoned PHPStorm and have been using VSCode for the last week or so, and no more problems with WSL crashing, it has been rock solid ever since. |
|
I'm on 22000.918 I do get an error after hibernate wake: Only a full restart fixes it! 👎 |
|
On Windows OS Build 22000.918, I am also getting a freeze of WSL2 on return from hibernate. CPU use is high: I also can't stop the service: WSL doesn't respond at all (listing doesn't work, status doesn't work, version doesn't work): I am using the latest WSL release 0.66.2. Restart works to bring things back but that is all that works. |
|
rowleya you may to try update Docker Desktop for last version (v4.12) #8703 In my case I have same problems with WSL2 and hibernate behavior. I tried to turn off hibernation but looks like my laptop dont support S1-S3 sleep mode. So updating the Docker fixed vmmem leak, but not wsl2 stucks after waking up. |
|
I don't have Docker Desktop installed here as I use docker on WSL2 when needed. Note that there isn't a vmmem memory leak here; that is just how much memory I am using! Of interest, I usually use eclipse within WSL2 and leave that running when hibernating. That had been working until recently, but with the issue, it also meant that the CPU usage of VMMem went very high when restoring from hibernate. On Friday I closed eclipse before hibernating, and on coming back this morning, the high CPU is gone, but WSL still won't start up again without a restart of the computer. |
|
OK, even more interesting, I saw a thread about collecting wsl logs, so I tried to do that this morning, running the process just before hibernating. It seems that the issue didn't then show up. I don't know if this means that it is something to do with the amount of time of hibernation or something... I will try to remember to run the logging process tonight again and see what happens tomorrow... |
|
It happens also to me: WSL: 0.66.2.0 After hibernation (not sleeping), VmmemWSL eats 100% CPU, there is no way to shutdown, terminate or restart. I also do not see any memory leaks (memory usage is reasonable). |
|
"Working" was said a bit too soon. It was running, but it was slow! A restart has fixed that again, but I do wonder if something is slowing things down with hibernate and then by the time it comes back (if overnight for example), it has slowed down to basically nothing at all... |
I observe exaclty the same thing. After I turned on logging, wsl doesn't hang... |
|
Having the same issue. It must have started probably after a Windows Update around 2-3 weeks ago as it worked before. |
|
As expected, WSL had frozen on return from hibernate this morning. I have attached the logs gathered during this time, started just before I entered hibernate, and stopped after returning; I did also try to start a WSL terminal just before stopping to ensure it was frozen. Eclipse was also open during this time but non-responsive on return (I could see the window and contents, but couldn't do anything with them). The logs are attached below: |
|
From the log, it seems the issue is likely related to the Microsoft Windows Host Network Interface Service, onRundown event, which seems to go into some sort of overdrive... |
|
Progress this morning. Further investigation of the virtual network interfaces, I seemed to have VirtualBox installed. I think this was installed by an IT administrator when they set up my laptop as I didn't install it myself. Anyway, having removed this, it seems that things are better on resume from hibernate. WSL is still responsive, though Eclipse was still running poorly. Restarting WSL seemed to then fix all the speed issues, which is a big step up from having to restart the machine! |
|
( same issue... uninstalling last win11 update "helped" ) |
|
I observe more or less the same behavior. My configuration:
Behavior
"Workaround"
|
|
I did another Windows update yesterday and am now on 10.0.22000.978. Unfortunately this seems to have brought back the issue again; once again the system resumes from hibernate with VmmemWSL running at high CPU but all of WSL being non-responsive. This time I managed to find a better workaround than restarting the PC though. If I kill the "Windows Subsysem for Linux Preview" process then WSL stops. I then have to manually start the LxssManager process which appears to have stopped (maybe this is the cause of the issue?). Once I do this, I can once again start WSL as if nothing had happened. I note that LxssManager is set to start "Manual". I don't know if this is the correct setting, but then I can't change it to "Automatic" as I get an error "Access Denied" if I try. Any comments on this front are welcome... |
|
Same issue here on my laptop after hibernation. |
|
Having the same issue. Build 22000.978 |
|
Started happening to me just after the last windows update. Build 22000.978 |
Thank you! Works for me. Key is to close all wsl* processes |
|
Same problem here on Build 22000.978, |
|
Have the issue with unresponsive WSL after hibernating. I have Docker Desktop installed. Usually what fixes the problem for me(without reboot) is My system is:
|
|
I also find this issue. Behavior
System info
|
|
@ZhehooMorgen referring you back to two of my older replies incase it helps. First the earliest versions of Windows and WSL when this issue stopped happening for me: And if you're unable to perform a system update to Win 11 - here's what I use to do on Win 10 to recover from the issue without a reboot: Good luck! |
|
I am seeing similar behaviour to this, however not on hibernate Unless I actually run |
|
Hi, I have same issue WslLogs-2024-08-03_11-41-58.zip
|
|
Having the same issue with WSL2 and Ubuntu 24.04. Only happens after a lengthy period of hibernation, but does not always happen. Vmmem CPU usage at 100% and WSL unresponsive until restarting / killing all WSL processes. Given that this seems to be a 2 year old thread with 0 responses from MS I do not have high hopes that this is going to be resolved any time soon. |
@KevinWilson-Linney , it's being worked on, and I have hopes that it is going to be resolved soon. :-) |
|
Hi everyone. I just got my problem solved by changing autoMemoryReclaim to dropcache instead of gradual. This issue seemed to be a reason. #11066. If your WSL hangs and you have Docker Desktop - just check - may be it's resource saving mode. Here is my config which works |
Just chiming in that I'm on an i7-10750H and being driven mad by this issue :-( |
Interesting, I was somehow convinced it was the CPU generation that had a role, at least in my case it did. Can you please add to https://docs.google.com/spreadsheets/d/10ML3KBdtINHYe8rSvat7JR_luVf1IeSammuAGVI983Q/edit#gid=0 ? |
Done! Just noticed that the spreadsheet does not capture the WSL distro - I took the liberty of adding a new column to capture that information, but feel free to delete it if you think it is irrelevant. Note though that there is a documented issue with Ubuntu 24.04 which is similar to this one (in the symptoms at least), documented here). I had faced that issue, but everything was good for me since moving to 22.04, until last week, when I started seeing this problem after an apt update+upgrade (which may or may not be related) |
|
Just had an similar issue where all WSL processes crashed on resume from hibernation which includes: terminal sessions, docker desktop and all VS Code sessions started from WSL. Eventually I could start a new sessions but not straight away, there were lots of errors from RestartManager in the log, but no new history events from windows update. I couldn't get VS Code to restart without a reboot as it complained about missing wsl directories. After a reboot terminal gave an error about missing default session and I had to reconfigure. I suspect something performed some updates and didn't restore tihngs correctly, but I can't find out what, nothing in update history. |
|
Actually even though its not listed in Settings -> Windows Update -> Update History it did apply an update. I found it in Event Viewer -> Windows Logs -> Application So in my case it had applied a WSL upgrade, without prompting or any sign in the main update history but that seems to be triggered when the machine starts up, its likely not limited to hibernation but as hibernation is the only time that existing sessions would be running it's the one people will likely see more adverse effects. I wonder if some of the other reports are caused by these silent updates? |
|
I'm running into this even without a hibernate. If I analyze wait chain on wslservice.exe (from the Task Manager details tab), I see it waiting for dllhost.exe. I can end the dllhost.exe thread from there and WSL starts working again, but will eventually stop due to waiting on the same dllhost.exe thread. Doing a stack trace of that thread, it's stuck on vp9fs.dll: |
|
@OneBlue So far 2.3.24 does seem to have fixed the issue! I'm not sure if it's the same as the original issue (since I was seeing it before hibernating as well), but FWIW it appears to be working after hibernate as well. |
|
Hi, I see same behavior on the latest version of wsl cat .wslconf
WSL not respond to the |
I tried to use "dropcache", but the next day after restarting the laptop, the result was the same. I open the laptop and the WSL stops after about 60 minutes. |
|
Update: I still face this issue on version 2.3.24.0 Primarily when starting or stopping WSL, so I try to keep it always running. If I face the issue, it tends to resolve itself without intervention after 10-15min, but the host machine is unusable until it does. |
|
Same here. After closing the notebook over night WSL hangs after spawning from hibernation and mounts from within the distro (f.e. /mnt/c) aren't available anymore. PS C:\Users\MYUSER\Downloads> wsl --version Docker Desktop is installed on version 4.23.0 (120376). But |
Its absolutely great, the more info the better! Thanks. TBH I started it about a year ago, but hasnt had the traction & user contrinutions I would think it would.... It needs more columns for sure.... when I started it I thought the CPU generation was the issue, but I think its not....
Interesting, cause I have both Ubuntu 22.4 & 24.4 installed and running, and hibernate works great on my new HP Omen Laptop i5-13500HX PS C:\Users\agelo> wsl --version BTW, I'll add it to the sheet ;-) |
|
So... +1 with the same problem here... hehe |
|
For anyone seeking a temporary solution: https://github.com/carlfriedrich/wsl-kernel-build |
|
Yes. We have deployed the patched kernel to more than six developers and the problem is gone.
It's the only solution available. |
|
Workaround for me: |
|
Nice.Have you tried sending the bill to Microsoft? Because they should be doing this work./PontusSent from my iPhoneOn 20 Nov 2024, at 12:25, Tiago ***@***.***> wrote:
Workaround for me:
taskkill /f /im wslservice.exe
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
my WSL updated to 2.3.26 , if anyone is frisky about testing it. At this point I've accepted it will never be fixed and just pop in here every few months to see if just maybe it might have. |
and others
Version
Windows 11 Pro 21h2 build 22000.832
WSL Version
Kernel Version
5.10.60.1
Distro Version
Ubuntu 2-.04
Other Software
Docker desktop windows
Repro Steps
Hibernate machine
Start up windows
open a new terminal
Expected Behavior
Shouldn't hang
Actual Behavior
No response, terminal hangs. wsl --shutdown from command prompt also hangs, only solution is to restart the machine.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: