|
Problem description: Sometimes WSL2 just hangs. Seems to happen more often when I've been away from the computer for a while, possibly related to it suspending? I have to reboot 3-5 times a day. Which, I will admit, is less often than the last time I used Windows in 1990. I'm comfortable poking around this thing, I just don't know where to start with Windows. Ideally there is some way to track down what's causing it to hang, so I can figure out how to prevent that condition? Maybe? This is smoke and mirrors to me right now. Attempted fixes: When this happens, frequently vmmem is taking a lot of CPU. I tried launching the task manager and killing vmmem, but it says I can't (I'll post the exact text next time it happens, in case that matters). I guess this is like when you send a kill -9 and it's stuck in the kernel? I've tried running code:
code:
I can reboot, wait 2-5 minutes for it to shut everything down, and all's good when it comes back up. This is annoying, though. Recent changes: I mean, I understand why this question is in the template, but this has been happening for months now, so, nothing recent has led to it. Maybe something did months ago, when I was setting up WSL2. Maybe it's related to the kludge daemon I had to install to get DNS to work with my corporate VPN: that looked like it called back to the Windows kernel somehow. I didn't understand what it was doing, but it worked. Could that freeze the entire VM system in the host OS? -- Operating system: Windows 10 System specs: HP Elite Dragonfly G3, with 16GB of RAM, soldered onto the motherboard (I can run one whole VM at a time!) Location: United States I have Googled and read the FAQ: Yes Thanks, fellow nerds! cruft fucked around with this message at 23:50 on Oct 20, 2023 |
# ? Oct 20, 2023 23:34 |
|
|
# ? Jun 3, 2024 22:30 |
|
It never freaking fails. I search every phrase I can think of, try all the magic incantations I find on Stack Exchange, give up and post a request for help, then I find the exact issue I just posted about. https://github.com/microsoft/WSL/issues/8529 I'll report back if I can verify that killing wslservice.exe fixes the problem. I presume wslservice provides Windows resources to Linux: for instance file system access, and maybe an X server that draws on Windows.
|
# ? Oct 20, 2023 23:49 |
|
Running this in an admin powershell did the trick:code:
|
# ? Oct 23, 2023 17:17 |