Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU - no container is running #2854

Closed
grongron opened this issue Nov 6, 2018 · 11 comments
Closed

High CPU - no container is running #2854

grongron opened this issue Nov 6, 2018 · 11 comments

Comments

@grongron
Copy link

grongron commented Nov 6, 2018

  • [x ] I have tried with the latest version of my channel (Stable or Edge)
  • [x ] I have uploaded Diagnostics
  • Diagnostics ID: 5232FBE1-3F49-4855-8E85-30DFC6CF4564/20181106152429

Expected behavior

low cpu when no container is runnig

Actual behavior

In Task manager: 30-30% CPU due to docker
Docker for windows Service: 18% CPU
WMI Provider Host: 14% CPU

"Quite Docker" and the CPU is back to 2-3%

Information

  • Windows Version: OS Name Microsoft Windows 10 Enterprise, Version 10.0.17134 Build 17134
  • Docker for Windows Version: 18.06.1-ce, build e68fc7a

Steps to reproduce the behavior

  1. Enable Hyper-V
  2. Install docker for windows
  3. Start docker
@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d 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

@qrzbrz
Copy link

qrzbrz commented Feb 7, 2019

WMI Provider logs the problem to EventViewer. After you start Docker Desktop open EventViewer (Windows+R, eventvwr), then in View Menu show Debug Protocols, then go to Microsoft->Windows->WMI Host. There you can find a lot of 5858 Events that show that Queryies are not closed properly by Docker.

@TheBlusky
Copy link

Were you able to do anything about it ?

@qrzbrz
Copy link

qrzbrz commented May 14, 2019

No, sorry I am not a docker-developer, only a user. My solution was to install an Ubuntu partition for using docker. Anyway, Windows 10 will soon get a linux kernel.

@qrzbrz
Copy link

qrzbrz commented May 14, 2019

/remove-lifecycle stale

@nicolas-tg-ch
Copy link

I have the same problem on Windows 10 Enterprise, Version 1803
Docker Version 2.0.0.3 (31259), Build 8858db3.
Is there anything one can do to fix the cpu load issue?
see also #809

@vlad-saling
Copy link

vlad-saling commented Jul 5, 2019

Have the same issue. VMI Provider Host keeps consuming CPU even if Docker Desktop is turned off. So once I stop working with Docker I use a temporary workaround described @ https://www.drivereasy.com/knowledge/wmi-provider-host-high-cpu-usage-on-windows-10-solved/#3 . Do not have a fix for CPU consumption during work though :/

@nicolas-tg-ch
Copy link

the fix for the cpu consumption is described in #809 (disable dummy network adapters via settings -> network -> status -> change adapter options)

@vlad-saling
Copy link

@nicolas-tg-ch I've tried that before, no change. I only have 2 Hyper-V adapters there. I tried to disable only one or both of them, yet VMI Provider host consumed about the same amount of CPU regardless.

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d 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

@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Jul 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants