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

Running Docker For Windows causes High System CPU utilization #220

Closed
shawngib opened this issue Nov 11, 2016 · 32 comments
Closed

Running Docker For Windows causes High System CPU utilization #220

shawngib opened this issue Nov 11, 2016 · 32 comments

Comments

@shawngib
Copy link

Expected behavior

Run Docker for Windows with normal CPU utilization.

Actual behavior

System Process runs t constant 25%+ CPU after starting DfW even after stopping DfW.

  • System Process - ntoskrnl.exe!RtlClearBitsEx+0x1fa0 25+ CPU

Information

  • Diagnostic ID from "Diagnose & Feedback" in the menu.
    56160023-9F47-4343-972F-7BF79976FD1B/2016-11-11_10-54-09

  • a reproducible case if this is a bug, Dockerfiles FTW
    Start DfW

  • page URL if this is a docs issue or the name of a man page
    N/A

  • host distribution and version (Windows version, build number, etc)
    Windows 10 Enterprise Insider Preview Build 14967.rs_prerelease.161107-1700

Steps to reproduce the behavior

  1. Install DfW beta
  2. Run DfW beta
@nmelnick
Copy link

For those triaging the issue, this "appears" to be a Hyper-V related issue in the latest Insider Preview builds, and may not have anything to do with Docker. Someone with a non-preview system may be able to help verify.

@friism
Copy link

friism commented Nov 18, 2016

I've seen this too - I'm no longer seeing it with 14971 which showed up yesterday

@mogest
Copy link

mogest commented Nov 20, 2016

Can confirm I'm also seeing this problem as reported on 14965. Thanks for letting us know it's fixed in a later build, @friism.

@kamkie
Copy link

kamkie commented Nov 22, 2016

i have this same problem on 14971

@michaeldaw
Copy link

I am also seeing it on 14971.

@friism
Copy link

friism commented Nov 30, 2016

Yeah, I see it too now on closer inspection.

Pinging @PatrickLang and @enderb-ms for ideas...?

@rn
Copy link
Contributor

rn commented Nov 30, 2016

FWIW I see the same issue on three machines (all on fast ring insider builds 14971.1000). In my case the thread consuming most of the CPU is at (my include typos as I could cut and paste):

ntoskrnl.exe!RtlAvlInsertNodeEx+0x20b70

This is not related to Docker for Windows as I see the same issue when starting other Hyper-V VM after a reboot without starting Docker for Windows. I'm therefore closing this issue, but:

  • it would be good to get a comment from @PatrickLang or @enderb-ms
  • you may want to provide feedback via the Insider feedback mechanism
  • I've posted a question on the insider forum here. You may want to "Me too" it or provide additional information.

Thanks for reporting

@rn rn closed this as completed Nov 30, 2016
@friism
Copy link

friism commented Nov 30, 2016

Thanks @rneugeba

@treeder
Copy link

treeder commented Nov 30, 2016

Did anyone figure out a way around this besides reinstalling non insider build of Windows?

@PatrickLang
Copy link

Did anyone open feedback and submit logs using the Windows Feedback tool on this? Once it's filed I can ping someone on the Windows Insider team to make sure it's triaged. I don't have any machines running 14971 at the moment

@PatrickLang
Copy link

Ah - found one "Hyper-V "system" still spinning CPU (one thread) now in RtlAvInsertNodeEx Build 14971"

If you're hitting this issue, search for and upvote it. in "Feedback Hub"

@treeder
Copy link

treeder commented Nov 30, 2016

Good find @PatrickLang . Here's the direct link to that in Feedback Hub: http://aka.ms/T0a5bo

@rn
Copy link
Contributor

rn commented Nov 30, 2016

@PatrickLang thanks. Up-voted. I also provided feedback via the insider feedback thing yesterday. Let me know if you need anything else.

@PatrickLang
Copy link

We have a fix on the way for a future Windows Insider build. Not sure what the date or build number will be until it's out though.

@PatrickLang
Copy link

A new build was just released: https://blogs.windows.com/windowsexperience/2016/12/07/announcing-windows-10-insider-preview-build-14986-pc/ If you have problems, please go ahead and open a new issue on it.

@friism
Copy link

friism commented Dec 8, 2016

@PatrickLang fixed it for me!

❤️

@rn
Copy link
Contributor

rn commented Dec 8, 2016

@PatrickLang thanks for the heads up. I can confirm that the update fixed the problem for me.

@Pjstaab
Copy link

Pjstaab commented Dec 17, 2016

Is there a way to force this build? Windows keeps telling me it might take a day or two to receive a new build but I still am not having any luck. I am on the insider fast ring.

@PatrickLang
Copy link

14986 was recently deployed to Windows Insider - Slow as well. Are you still waiting on it?

I think they will release an ISO here eventually, but it's still showing 14965.

@Pjstaab
Copy link

Pjstaab commented Dec 20, 2016

I'm definitely still on 14965. I get the emails saying new builds come out but I'm not getting any updates on my computer. I've unsubscribed and resubscribed to the channel too and have waited a few days.

@PatrickLang
Copy link

@Pjstaab I'm sorry it's not working out. Unfortunately Windows Update is out of my area of expertise so I don't think I can help with it here. The best option for finding a solution is to check posts here or create a new one: https://answers.microsoft.com/en-us/insider/forum/insider_wintp

@Pjstaab
Copy link

Pjstaab commented Dec 21, 2016

I'm not in a horrible rush, just though on the off chance that someone knew something I could kickstart it but it's not the end of the world.

@treeder
Copy link

treeder commented Dec 29, 2016

@Pjstaab did you change to the fast ring of the windows insider builds? You need to do that.

@Pjstaab
Copy link

Pjstaab commented Jan 3, 2017

@treeder I've been on the fast ring, tried switching to slow for a day and then back to fast, nothing seems to work.

@propagated
Copy link

propagated commented Apr 14, 2017

After installing docker for windows on windows 10 1607 (14393) I have a svchost.exe running at a constant 25% cpu. I've pinned it down to the windows management instrumentation service which is bound to the hyperV services i let the docker installer enable.

@Pjstaab @treeder any non windows insider workarounds to be had?

@jjloesch
Copy link

Same issue is still there using latest Win 10 ver 1709

@kratos4ever
Copy link

Hi, Any updates on this issue?

@wintercounter
Copy link

Same here.

@industrial64
Copy link

Issue persists = no resolution here ^ .

@maeglindeveloper
Copy link

Hi everyone, have the same issue with vpnkit.exe.

image

@cforce
Copy link

cforce commented Oct 9, 2018

same here.

@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 Jun 19, 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