Vmmemwsl - High CPU Usage

[stumarr]

Version

Microsoft Windows [Version 10.0.22000.1098] / WSL version: 0.70.4.0

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.15.68.1

Distro Version

20.04.5 LTS

Other Software

n/a

Repro Steps

After computer wakes up from sleep, wsl does not respond.

Expected Behavior

WSL to respond after waking up computer from sleep without rebooting.

Actual Behavior

Windows responds slowly and checking task manager, CPU usage for the vmmemwsl process is spiking.

Attempting to kill the process from task manager does not work as I get 'Access denied', even if I run task manager as Administrator. Same result from the command prompt. When I run 'wsl.exe --shutdown' from the command prompt, it just hangs and never completes. The only way to recover WSL is to reboot. I've tried a fix that I found in a forum that suggested adding the lines below to the .wslconfig, but still does not resolve the issue.
[wsl2]
guiApplications=false

I was unable to upload the log in the 'Diagnostic Logs' section below so I placed it here.
WslLogs-2022-10-28_08-40-49.zip

Diagnostic Logs

No response

[Perksey]

I've also been getting this recently! So glad it's not just me.

[LiaraAlis]

I think this is a duplicate of #6982.
I also have this issue and still not resolved.

[stumarr]

Not sure if you were able to send logs of the issue, but I was able to capture them while the issue was happening. Hopefully, we can get a solution. It's frustrating, as it happens almost daily.

[Perksey]

Yep, happens whenever I hibernate my laptop which is very often!

[heigum]

I also start every day with this issue if I forget to shutdown wsl before I end my day.

Update, discovered late yesterday that WSLg (10.0.26) Preview had snuck in under apps and features (again) after uninstalling it I have had no further problems with this. And thinking back a month or so (067.06) I had the exact same issue, which I fixed the same way.

[OneBlue]

/dupe #6982

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

[asalaneck]

I am still getting this issue, has it been resolved?

[LOuroboros]

I just had this same problem happen to me. This issue didn't even let me boot up WSL again, so I was forced to reboot my PC.
Relevant specs:

WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1194

[tcarolan]

I experience this same issue. Getting my computer back from hibernation is impossible. Thought it was hardware, but its been VmmemWSL the whole time.

[hima-gadupudi]

Same problem as @tcarolan mentioned. Getting my computer out of hibernation everyday morning is impossible. VmmemWSL is taking too much CPU

[obar1]

anybody tried already playing with .wslconfig to mitigate ?
https://learn.microsoft.com/en-us/windows/wsl/wsl-config#example-wslconfig-file
like disabling GUI if not needed and set processors param?

[YAmikep]

anybody tried already playing with .wslconfig to mitigate ? https://learn.microsoft.com/en-us/windows/wsl/wsl-config#example-wslconfig-file like disabling GUI if not needed and set processors param?

@obar1 I limited processors to half of what I have but then I have WSL sucking 50% of my cpu anyway which slows down everything...
As for the GUI, I am using it so did not try to disable it.

[theritz1990]

need to run cmd as admin and type "wsl --shutdown" don't even need to close docker if you are running it. it should immediately throttle back. do a system restart and you should be good.

[Sangresz]

I dont know if my problem relates to this issue or not but i have Vmmemwsl process active and i can't even run wsl --shutdown because it just hangs there

Edit: This solved my problem