High CPU usage for vmmem

Steve Lo 100

Hi,

I have experienced high CPU usage for Vmmem frequently (~every 2days) and the only solution at the moment is simply restart my machine.

It is understood that is related to WSL and I do have a Docker image running on Ubuntu on Windows. However it is not really responding for Ubuntu and Docker (see below) and CPU usage is still that high even I manually close Docker Desktop and run cmd wsl --shutdown.

It's really disruptive for me and any opinion would be appreciated.

Cheers

Steve

User's image

Kesims 30 Reputation points

2023-05-10T15:20:48.76+00:00

Hello, I can confirm the issue! Also running WSL2 with Docker, exactly the same issue. Sometimes the WSL just bugs and uses 100% of my cpu, making the computer basically unusable. Only restart of the whole system helps, I have not figured out a way to restart just the vmmem thing... I have a limit on memory for WSL, but while putting a limit on processors could treat the symptoms, it is definitely not going to fix the root issue.

Also from my experience, when this bug occures, things using WSL (Docker) stop working. It is really annoying and if programs such as Adobe or Fusion 360 did not held me on Windows, I would already happily move to Linux full time - now I am running dual boot and crying every time I have to use Windows...
Jiri Hajek 15 Reputation points

2023-05-26T14:34:51.1166667+00:00

The very same issue here. I also use WSL2, but the issue happens sometimes even if I haven't used WSL since reboot! The closest to WSL I have used is VSCode with WSL Extension, but this one was only loaded by VSCode, not actively used.

CPU usage spikes to 100% for no apparent reason, the last time when browsing in Chrome.
M$_Sucks 30 Reputation points

2023-05-30T13:41:18.4466667+00:00

Same here. What really helps is to reinstall wsl, which can be a very painful solution. Especially, if you have carefully tuned up your setups on your wsl.
Jasso Miroslav 0 Reputation points

2023-06-26T09:17:20.2166667+00:00

Same issue here. It stared after some of the last Windows updates. About 2 weeks ago. The only one solution is to restart my computer. It is really annoying, because it happens every 2-3 days.
Tim W 25 Reputation points

2023-06-28T09:56:58.1+00:00

I have this problem as well, having installed Docker and WSL2 a few days ago to test some docker containers, I now find my CPU usage for vmmem stuck on 49%, dragging down laptop performance, even though I have no containers running. Stopping all the services for linux processes seems to clear this, but is not an ideal solution.
Mike G 0 Reputation points

2023-06-28T21:42:25.8866667+00:00

In trying to resolve this issue the wsl --shutdown command never completed. I had to reboot to temporarily resolve it. I have experienced this a couple times before and atm expect to have to reboot to resolve. Please help.

Windows 11; WSL2; Docker for Windows with WSL integration for use with VS Code
Daniel 11 Reputation points

2023-07-12T19:17:08.38+00:00

I have also been having this problem for weeks now. I also use Docker and WSL2. Everything everyone says here is exactly what I'm experiencing, and it only started fairly recently (last month or two, not exactly sure when but it's recent).

I've also been rebooting to resolve this, but I just tried to "End Task" the Windows Subsystem for Linux process as someone WFarmer suggested int he answers section, and it dropped the CPU from 100% down to about 5%, so I can at least confirm that workaround works without having to completely reboot. It's still very disruptive though since I regularly use WSL2 for development and this has caused some issues there more than once, including loss of active work.

Please fix this, Microsoft!
1gor 0 Reputation points

2023-11-04T08:49:57.1333333+00:00

Hi there!

Guys, all of you have Intel CPU or Ryzen?
Please link your CPU in comments to understand is this CPU problem.
I have hybrid CPU intel 12500H.
PLEUN SAARLOOS 0 Reputation points

2024-02-16T10:05:56.57+00:00

I had the exact same problem on my laptop.
I solved it by removing the charger and now I can run wsl and docker as normal. I hope someone smarter finds a better solution.
Alex Herlan 0 Reputation points

2024-03-27T03:08:43.76+00:00

I am having the same issue. AMD Ryzen 5900 series CPU, 32gbs DDR4, Windows 11 64bit. Running Docker. Only started occuring after this most recent Windows Update. :-. Anything to do with WSL, virtualization, etc. Has been a huge pain to deal with on Windows 11. I am not a happy customer at all.

15 answers

WFarmer 35 Reputation points

2023-06-07T15:54:52.5933333+00:00

Hi All,

I use Docker and WSL2 frequently and have run into this problem many times. It seems to happen semi-randomly after some period of time, ~1-2 days.

I don't have a solution that addresses the core issue with Vmmem but I do have a workaround that doesn't require rebooting my whole machine. For me, going into Task Manager and ending the "Windows Subsystem for Linux" task is sufficient and Vmmem goes back to normal.

Hope this works and saves people from having to restart every time.
Please sign in to rate this answer.

7 people found this answer helpful.
M$_Sucks 30 Reputation points

2023-06-08T10:13:59.84+00:00

I don't think this is possible (at least on my Win11 PRO it is refused), but if I go to power shell (as admin) and type

wsl --shutdown

that takes some time to process, but usually works..
https://www.how2shout.com/how-to/how-to-reboot-wsl-windows-subsystem-linux-in-windows-10.html

Jiri Hajek 15 Reputation points

2023-06-16T08:52:10.7633333+00:00

Thanks for sharing WFarmer, I can confirm that it works. The 100% utilization just happened to me and termination of wslhost.exe fixed the issue (Win10). So, as you wrote, not a solution, but a good workaround.

Max F 0 Reputation points

2023-06-25T22:11:55.5666667+00:00

Didn't work for me, exited wsl but vmmem still using 100% CPU and impossible to kill.

Hongjune Kim 0 Reputation points

2023-06-28T21:06:39.35+00:00

I cannot find any "Windows Subsystem for Linux" process, since I have closed all WSL instances, and wsl --shutdown, even if in administrator account won't respond. The vmmemSWL is still taking up 75% of CPU and cannot do anything else but reboot my system.
Sign in to comment
Walker, James (SI BP AM R&D SYS) 15 Reputation points

2023-07-17T13:47:30.0733333+00:00
Open cmd prompt, run as admin,

wsl --shutdown
Please sign in to rate this answer.

3 people found this answer helpful.
Wirawan Purwanto 0 Reputation points

2023-07-27T11:40:42.14+00:00

This solution does not work for me. I had docker running when this incident happened too. It is on a laptop that was kept on for a while (but put to sleep / hibernation whenever not in use or in transit). Suddenly the CPU utilization went to the sky and there was nothing I could do to the machine except to restart it. "wsl --shutdown" does not work since this is a work laptop and I don't have a real admin privilege. They installed "MakeMeAdmin" tool here, but it does not properly shut off WSL2.

S. Munoz 5 Reputation points

2023-08-22T16:00:07.7933333+00:00

Usually running wsl --shutdown works for me, but not this time and neither did attempting to stop service WslService or resetting the video driver (Win+Ctrl+Shift+B). The shutdown command just hung and attempting to stop the service left status at "Stopping". I was forced to reboot this time.
Sign in to comment
Petr Bodnár 20 Reputation points

2023-07-23T10:22:01.23+00:00

Note that this bug seems to have been discussed at https://github.com/microsoft/WSL/issues/6982 for over 2 years already. From there, it looks like pressing Win+Ctrl+Shift+B could also help, as it resets the graphic (video) driver which apparently causes the issue.

As stated by WFarmer, stopping the Window Subsystem for Linux (wslhost.exe) should work as well. In the linked thread, restarting the Windows service called WslService could help as well.

Of course, none of this helps with avoiding the issue altogether, unfortunately.
Please sign in to rate this answer.

3 people found this answer helpful.

0 comments No comments
Sign in to comment
Steve Lo 100 Reputation points

2023-03-22T19:18:54.26+00:00

Thanks for your answer, it's probably fix the symptom by scarifying the performance. However, any idea what is the root cause or how to figure it out? Particularly high cpu with unresponding Ubuntu and no docker running?
Please sign in to rate this answer.

1 person found this answer helpful.
Ajoy Bhatia 0 Reputation points

2023-06-19T23:06:47.51+00:00

Exactly what I am facing. WSL2 with Ubuntu not responding and have never run Docker. Still vmmem is using 75%+ CPU. I have not yet read anyone from Microsoft that vmmem high CPU usage occurs even without Docker

Petr Bodnár 20 Reputation points

2023-07-23T09:39:37.4933333+00:00

Yes, this bug seems totally unrelated to Docker - I've got the same problem, no Docker on my PC. Luckily the workaround described by WFarmer works for me (until the WSL goes nuts again, of course).
Sign in to comment
Nicolas Vallet 5 Reputation points

2023-12-18T10:25:41.0933333+00:00

At my level, I noticed that I have Visual Studio open in remote mode to WSL2 + Docker, every time it occurs. Most of the time, it happens just after I wake up my laptop from sleep mode.

If I shut down VS, who is trying to reconnect to the remote wsl session, shutdown docker, then shutdown WSL. Vmmem goes away and I can relaunch everything until the next time I put my laptop in sleep mode.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment