WSL high CPU usage and hangs all requests after some sleep-resume or hibernate-resume cycles #9855

MichaelXt · 2023-03-27T21:23:29Z

Windows Version

Microsoft Windows [Version 10.0.22000.1696]

WSL Version

WSL version: 1.1.3.0 Kernel version: 5.15.90.1 WSLg version: 1.0.49 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.1696

Are you using WSL 1 or WSL 2?

WSL 2
WSL 1

Kernel Version

Default Distribution: Ubuntu-22.04 Default Version: 2 WSL1 is not supported with your current machine configuration. Please enable the "Windows Subsystem for Linux" optional component to use WSL1.

Distro Version

Ubuntu 22.04

Other Software

During the sleep-resume or hibernate-resume cycles following software is running:
vscode: 1.76.2, WSL extension: v0.76.1
explorer with wsl drive open

Repro Steps

Use wsl with vscode, open drives in windows explorer, use other apps which use the filesystem from the WSL.
Do a lot of sleep-resume cycles, while other software accessing the WSL works.
Once in a while after sleep-resume notice that the VmmemWSL process CPU usage is high. Attempt to access the WSL FS via explorer - it hangs opening it, use vscode - it says WSL is not responsive.
Try to shutdown the wsl to restart it using wsl --shutdown - the operation hangs, never completes.

Expected Behavior

The WSL always works normally after sleep-resume / hibernate-resume cycle.

Actual Behavior

After some sleep-resume / hibernate-resume cycles the WSL hangs, CPU usage spikes, and WSL doesn't respond to any commands. wsl --shutdown doesn't stops the wsl, and just hangs.

Diagnostic Logs

No response

The text was updated successfully, but these errors were encountered:

thfrei · 2023-03-28T10:11:45Z

+1
Have the same issue with vmmem spking cpu usage.
However, wsl --shutdown will eventually close vmmem process and system returns to normal. Shutdown takes approx 1-2 minutes.

$>wsl --status
Default Distribution: Ubuntu
Default Version: 2

Windows Subsystem for Linux was last updated on 22.11.2022
WSL automatic updates are on.

Kernel version: 5.10.102.1

One trial to fix it was: I adapted the $USER/.wslconfig file according to: https://tkacz.pro/wsl-fix-vmmem-high-cpu-usage/ - However this solution does not really seem to fix the issue. Maybe it helps with shutdown working.

I read somewhere, that apparently it should not occur in Windows 11 anymore. Windows 11 also has some more wsl2 features like usb pass-through or mounting which is missing in Windows 10 :-(

ghost · 2023-03-28T21:16:46Z

Is this on arm64 or amd64?

MichaelXt · 2023-03-29T18:41:24Z

amd64

OS Name:                   Microsoft Windows 11 Home
OS Version:                10.0.22000 N/A Build 22000
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
System Manufacturer:       Micro-Star International Co., Ltd.
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 154 Stepping 3 GenuineIntel ~2900 Mhz
BIOS Version:              American Megatrends International, LLC. E1544IMS.505, 8/10/2022
Hotfix(s):                 6 Hotfix(s) Installed.
                           [01]: KB5022505
                           [02]: KB5008295
                           [03]: KB5012170
                           [04]: KB5019448
                           [05]: KB5023698
                           [06]: KB5022925
Network Card(s):           2 NIC(s) Installed.
                           [01]: Realtek Gaming 2.5GbE Family Controller
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                           [02]: Intel(R) Wi-Fi 6E AX211 160MHz
                                 Connection Name: Wi-Fi
                                 Status:          Media disconnected
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

YAmikep · 2023-04-01T18:54:26Z

This high cpu issue has unfortunately been around for a while and Microsoft is very silent on it. 😞
See this other issue from 2021: #6982

MichaelXt · 2023-04-03T21:03:28Z

WslLogs-2023-04-03_13-59-51.zip
uploaded the logs.

Couple differences:

The high cpu usage is permanent, and doesn't go with time, nor with any attempts to restart wsl (the restart hangs forever)
While the issue doesn't repro with each cycle, it does repro 2 out of 7 runs.

mrobbeloth · 2023-04-04T23:17:46Z

This seems like a power management issue as I regularly hibernate my system and this issue only makes itself evident coming out of hibernation (others have said sleep mode).

benreaves · 2023-04-17T18:32:55Z

@thfrei

One trial to fix it was: I adapted the $USER/.wslconfig file with guiApplications=false
... I read somewhere, that apparently it should not occur in Windows 11 anymore. Windows 11

I'm sorry to report, I had that line in .wslconfig, and I'm on Windows 11 (Dell XPS 17 purchased January 2022) and still had the vmmem 100% CPU problem.

rngadam · 2023-05-02T11:19:59Z

Just experienced the same thing this morning from sleep: (Ubuntu window unresponsive, wsl shutdown not returning, Visual Studio Code reporting containers not connected). Had to reboot.

WSL version: 1.2.5.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2846
Default Distribution: Ubuntu
Default Version: 2

rngadam · 2023-05-04T13:25:43Z

Duplicate of #8696 ? That one has a workaround to properly kill WSL without rebooting.

narbhar · 2023-11-10T06:48:32Z

I can confirm this issue too. Vmmem high CPU usage after sleep. I had a VSCode session that was running before and it says it is disconnected now. In powershell, trying out wsl.exe --shutdown doesn't work either. The command just hangs. I can't access the Ubuntu (the distro on WSL) terminal when the CPU usage high.

rngadam · 2023-11-10T12:06:30Z

I can confirm this issue too. Vmmem high CPU usage after sleep. I had a VSCode session that was running before and it says it is disconnected now. In powershell, trying out wsl.exe --shutdown doesn't work either. The command just hangs. I can't access the Ubuntu (the distro on WSL) terminal when the CPU usage high.

Have you tried this workaround:

taskkill /IM wslservice.exe /F

in a console running as administrator to restart the VM.

I keep using that command regularly to restart WSL.

i2van · 2023-11-10T18:34:18Z

Another workaround (requires PSTools):

pskill wslservice.exe & pskill wslhost.exe

daniel5gh · 2023-11-20T10:39:16Z

Having the same issue for a long time (1y+) on my laptop currently running:

WSL version: 2.0.9.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3693

This laptop I sleep and hibernate regularly.

On another machine that has always had win11 since installing WSL2, I never encountered this issue. This machine I only sleep regularly, hibernate is disabled.

I do not use vscode, I do use various IDEs from the JetBrains toolbox. But I always had a suspicion there was a link with docker-desktop, because when I run docker-desktop containers this issue occurs much more frequently. Today I noticed for the first time this issue occurred without docker-desktop running (which prompted me to search this issues thread once again).

My workaround used to be also like others report in this thread to use various ways to kill the WSL process, but since at least a few months I realized that just another hibernate/wake cycle also corrects the problem for the running WSL2 without having to restart WSL.

Hope that workaround works for you all too, as it is a lot more convenient than restarting WSL

rngadam · 2023-11-20T12:33:52Z

But I always had a suspicion there was a link with docker-desktop, because when I run docker-desktop containers this issue occurs much more frequently.

Note that in our case we specifically do not run docker-desktop but docker under WSL only and have the same issue.

My workaround used to be also like others report in this thread to use various ways to kill the WSL process, but since at least a few months I realized that just another hibernate/wake cycle also corrects the problem for the running WSL2 without having to restart WSL.

@daniel5gh interesting that another hibernate/wake cycle fixes this - thanks for the tip!

felixschndr · 2024-07-25T11:43:23Z

Has someone found a solution to this issue yet (other than another power cycle)? I am having to restart WSL after every hibernate which is about 2-3 times a day...
Did someone try reinstalling WSL yet?

TETYYS · 2024-07-28T10:23:44Z

Has someone found a solution to this issue yet (other than another power cycle)? I am having to restart WSL after every hibernate which is about 2-3 times a day... Did someone try reinstalling WSL yet?

There is no proper solution, Microsoft ignores the problem.

thfrei · 2024-07-28T12:04:05Z

Has someone found a solution to this issue yet (other than another power cycle)? I am having to restart WSL after every hibernate which is about 2-3 times a day... Did someone try reinstalling WSL yet?

In my case, I eventually switched to Windows 11. There the problem disappeared.

felixschndr · 2024-07-28T12:05:42Z

@thfrei Did you factory reset windows after/before upgrading?

thfrei · 2024-07-28T12:21:15Z

@thfrei Did you factory reset windows after/before upgrading?

nope..., kept everything as is, and then used https://github.com/valinet/ExplorerPatcher to stay sane 😅

ghost added the needs-author-feedback label Mar 28, 2023

microsoft-github-policy-service bot removed the needs-author-feedback label Mar 29, 2023

github-actions bot mentioned this issue May 6, 2024

Vmmem process suddenly and randomly takes close to 100% of CPU indefinitely #11561

Closed

2 tasks

github-actions bot mentioned this issue Aug 6, 2024

WSL2 gets laggy over time - suspend to disk (hibernate) restores normal operation #11885

Open

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

WSL high CPU usage and hangs all requests after some sleep-resume or hibernate-resume cycles #9855

WSL high CPU usage and hangs all requests after some sleep-resume or hibernate-resume cycles #9855

MichaelXt commented Mar 27, 2023

thfrei commented Mar 28, 2023 •

edited

Loading

ghost commented Mar 28, 2023

MichaelXt commented Mar 29, 2023

YAmikep commented Apr 1, 2023

MichaelXt commented Apr 3, 2023

mrobbeloth commented Apr 4, 2023

benreaves commented Apr 17, 2023

rngadam commented May 2, 2023

rngadam commented May 4, 2023

narbhar commented Nov 10, 2023

rngadam commented Nov 10, 2023

i2van commented Nov 10, 2023 •

edited

Loading

daniel5gh commented Nov 20, 2023 •

edited

Loading

rngadam commented Nov 20, 2023

felixschndr commented Jul 25, 2024

TETYYS commented Jul 28, 2024

thfrei commented Jul 28, 2024

felixschndr commented Jul 28, 2024

thfrei commented Jul 28, 2024

WSL high CPU usage and hangs all requests after some sleep-resume or hibernate-resume cycles #9855

WSL high CPU usage and hangs all requests after some sleep-resume or hibernate-resume cycles #9855

Comments

MichaelXt commented Mar 27, 2023

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

thfrei commented Mar 28, 2023 • edited Loading

ghost commented Mar 28, 2023

MichaelXt commented Mar 29, 2023

YAmikep commented Apr 1, 2023

MichaelXt commented Apr 3, 2023

mrobbeloth commented Apr 4, 2023

benreaves commented Apr 17, 2023

rngadam commented May 2, 2023

rngadam commented May 4, 2023

narbhar commented Nov 10, 2023

rngadam commented Nov 10, 2023

i2van commented Nov 10, 2023 • edited Loading

daniel5gh commented Nov 20, 2023 • edited Loading

rngadam commented Nov 20, 2023

felixschndr commented Jul 25, 2024

TETYYS commented Jul 28, 2024

thfrei commented Jul 28, 2024

felixschndr commented Jul 28, 2024

thfrei commented Jul 28, 2024

thfrei commented Mar 28, 2023 •

edited

Loading

i2van commented Nov 10, 2023 •

edited

Loading

daniel5gh commented Nov 20, 2023 •

edited

Loading