Closed hernandp closed 2 years ago
The kernel thread 108 is using the CPU by calling repeatedly KeBalanceSetManager, which can be caused by memory pressure. I analyzed a memory dump of my system and realized there were a lot (over 30000) of WSL.EXE processes seemingly dead -but each with 80kb allocated mem.
They were all created by docker backend process, e.g:
0: kd> !process 688 Searching for Process with Cid == 688 PROCESS ffffe784296c5080 SessionId: 1 Cid: 0688 Peb: 4683bf000 ParentCid: 4498 DirBase: 4fa68e000 ObjectTable: 00000000 HandleCount: 0. Image: wsl.exe VadRoot 0000000000000000 Vads 0 Clone 0 Private 15. Modified 5. Locked 0. DeviceMap ffffa90f59d5b1f0 Token ffffa90f72351060 ElapsedTime 20:36:27.640 UserTime 00:00:00.000 KernelTime 00:00:00.000 QuotaPoolUsage[PagedPool] 0 QuotaPoolUsage[NonPagedPool] 0 Working Set Sizes (now,min,max) (16, 50, 345) (64KB, 200KB, 1380KB) PeakWorkingSetSize 1902 VirtualSize 0 Mb PeakVirtualSize 2101308 Mb PageFaultCount 2021 MemoryPriority BACKGROUND BasePriority 8 CommitCharge 19 Job ffffe784332c20a0
Parent of that process?
0: kd> !process 4498
Searching for Process with Cid == 4498 PROCESS ffffe7842c84b300 SessionId: 1 Cid: 4498 Peb: ad5622d000 ParentCid: 2d74 DirBase: 513da3000 ObjectTable: ffffa90f63765800 HandleCount: 41579. Image: com.docker.backend.exe VadRoot ffffe7842c6bbd20 Vads 179 Clone 0 Private 6125. Modified 85188. Locked 5. DeviceMap ffffa90f59d5b1f0 Token ffffa90f633525f0 ElapsedTime 20:51:33.928 UserTime 00:00:49.046 KernelTime 00:02:00.531 QuotaPoolUsage[PagedPool] 929952 QuotaPoolUsage[NonPagedPool] 35440 Working Set Sizes (now,min,max) (10980, 50, 345) (43920KB, 200KB, 1380KB) PeakWorkingSetSize 14367 VirtualSize 4947 Mb PeakVirtualSize 4959 Mb PageFaultCount 872947 MemoryPriority BACKGROUND BasePriority 8 CommitCharge 10038 Job ffffe784332c20a0
Look at handle count :
Maybe this is caused by some problem where docker backend creates/kills a lot of dummy WSL.EXE processes in rapid succession.
Related issue https://github.com/docker/for-win/issues/12916
does the problem persist if you upgrade to Docker Desktop v4.12? This sounds a lot like - https://github.com/docker/for-win/issues/12877
Upgraded. Several hours without any issue. Let's hope 4.12 fixes it , thank you. I'll look again the next week as I'll be using Docker+WSL a lot.
Hooray! Closing as resolved.
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
Actual behavior
System Process CPU use >15%. Using ProcExp shows a thread of NTOSKRNL!Ordinal25+0x1730 address consuming cycles continuosly.
No containers running. Docker does not exit immediately if I request by UI.
Expected behavior
I expect low CPU use without containers running.
Information
Output of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
Steps to reproduce the behavior
Run Docker/WSL2 session e.g Terminal and wait until System process starts eating CPU.