High CPU usage while Docker Desktop is running on windows

[HenrikPoulsen]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: 4FDE0313-882E-40F4-BEAC-95C3BAEDEE00/20200529103928

Expected behavior

No CPU activity when no containers are running

Actual behavior

High CPU usage on the Vmmem process while docker desktop is running
16% constant usage on CPU Intel(R) Core(TM) i9-9980HK CPU, aka 8 core machine
Windows Task manager also reports "Very High" power usage from the process while Docker Desktop is running.

Information

• Windows Version: Windows 10 Pro 1909 - build: 18363.836
• Docker Desktop Version: 2.3.0.3 (45519)
• Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No. Running on non-virtualized Alienware m15 R2 laptop

Steps to reproduce the behavior

I have no help to give here. Started after updating to a new version of docker desktop and now won't stop regardless of what I do, other than shutting down docker desktop.

1. ...
2. ...

[mat007]

Thanks for the report, there is already a couple of people impacted by this in #6564 would you be OK to close this one as a duplicate?

[HenrikPoulsen]

If that is the process, then sure go ahead.

[flavienlaurent]

@mat007 not sure it's the same issue but it's not the same steps to reproduce. In my case, no wake after sleep is involved.
I restarted my laptop from scratch and vmmem is using 15/20% cpu all the time when the first container has started.

EDIT:
After 10minutes, vmem is using 0/5% cpu. Back to normal I guess?

[mat007]

Is this with the WSL 2 backend? If yes maybe it’s microsoft/WSL#4166?
Right, I checked the diagnostics and it’s Hyper-V.

[mat007]

@mat007 not sure it's the same issue

You’re right, that other ticket has Docker Desktop running in a virtualized environment.

[Pirozek]

Same problem with this one, vmmem is using like 25% of my CPU without any containers actually running.

Diagnostics ID 92D9DBBE-5255-4969-81BC-398999CD4434/20200609095906

[dem1tris]

Same issue on WSL2.
Vmmem utilizes 15-25% CPU just after Docker starts without any running containers.
com.docker.proxy.exe and Docker Desktop utilizes 2-5% CPU each.

"About" screenshot : https://user-images.githubusercontent.com/22416102/88632764-3e042e80-d0de-11ea-89d6-f4ef8aa5402d.png

Also, same as #6834

[wiggisser]

I have Docker Desktop (v2.3.04) installed on my Win10 Pro Machine. I even have the high CPU usage caused by the "DockerDeskop VM" when Docker Desktop is not started at all. Hyper-V Manager shows a constant CPU usage of 10% for that VM.

I didn't notice this in the past, so it might have started with one of the latest updates.

EDIT: I did downgrade to v2.3.0.2 and the problem seems to be gone ... Eventhough the DockerDesktop VM is running, Hyper-V Manager only reports a CPU usage of 1% (without any containers running) and the vmmem.exe process does no longer rank top in CPU usage in the Windows task manager.

[tcpiplab]

On Windows 10 Pro, downgrading Docker Desktop to v2.3.0.2 solved the problem where the Vmmem process was super high and running the laptop fan on maximum speed.

[wiggisser]

Anyone had a chance to try this on the new 2.3.0.5 release?

[yan-hic]

W10Pro here - not using Hyper-VM as I run DockerD in WSL - and 2.3.0.5 still makes Vmmem go off the chart.

For what it's worth, I have just uninstalled 2.3.0.5 and installed the edge 2.3.6.2 instead, and all back fine ! At least for now.

[wiggisser]

Installed docker desktop 2.4 stable today. Didn't notice any extra CPU usage until now ...

[Pomax]

Also noticing 2.4 being surprisingly more cpu intensive compared to before, with vmmem using 40% cpu, and COM Surrogate (which is only active while Docker's running a container) at 25%, so something really weird is going on here because that much cpu for the COM process when nothing's happening in the container is a guaranteed bug.

[jacol84]

I have the same problem

I don't have any container running

665 root 12:04 /usr/local/bin/dockerd --containerd /var/run/desktop-containerd/containerd.sock --pidfile /run/desktop/docker.pid --config-file /run/config/docker/daemon.json --swarm-default-advertise-addr=eth0
and
32 root 5:20 /usr/bin/vpnkit-bridge --pid-file=/run/vpnkit-bridge.pid --addr=stdio guest

my windows version

Microsoft Windows NT 10.0.19042.0

update wsl2 now is working
FIXED

[bradparks]

I have Docker Desktop running on mac, and it sporadically will make my system crawl. I was originally running a slightly older Docker desktop with the same issue, and upgraded to 2.5, but same issue persists.

[Pomax]

@bradparks this is the for-win repository, for the windows-specific build.

[bradparks]

whoops ! sorry - I googled and this came up, and I never noticed that it was Windows specific - my bad!

[acurvers]

any news on this the issue still persists

[caot]

It took the cpu around 25% of Windows 10. Docker is updated.

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[Pomax]

@wallyhall If you're going to unstale an issue, at least add more details, because you just pinging everyone with a "me too" for an issue that's basically moot. It'd be far better to file a new issue, with your new problem description, both so docker folks can look at it in relation to what Docker looks like now instead of several versions ago, and for all the people you just pinged.

[wallyhall]

@wallyhall If you're going to unstale an issue, at least add more details, because you just pinging everyone with a "me too" for an issue that's basically moot. It'd be far better to file a new issue, with your new problem description, both so docker folks can look at it in relation to what Docker looks like now instead of several versions ago, and for all the people you just pinged.

Accept my apologies, I thought reopening an issue which "went stale" after nobody mentioned it for 90 days (while it appears to still remain) was the most helpful thing to do - confirming that the issue quite possibly still exists 18 months later, with 24 people presumably indicating they personally still had the issue only 6 months ago.

New issue raised, because for me at least - it's far from basically moot. (It renders my machine fairly loud and sluggish unless I quit Docker Desktop ;-) )

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked