Vmmem suddenly using too much CPU when idle

[ad-on-is]

Windows Build Number

Windows 21364

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.16.3-microsoft-standard-WSL2

Distro Version

Ubuntu 21.04

Other Software

Docker Desktop 3.1.0 and 3.3.1

Repro Steps

After updating to Windows 21364 and wsl --update I noticed how my fans went crazy after a restart, which is pretty unusual, even that I start Docker automatically after boot.
Inspecting Task Manager, I can see that Vmmem isusing ~ 20% of my CPU and 4/32 GB RAM, when Docker is running.

Also typing in Windows Terminal, would skip key-strokes very often.

The overall CPU usage is at 40%, every other service after "Service Host" uses up to 0.2% CPU.

The fan noise when idle is so loud as if I was gaming.

After quitting Docker it drops to 7%CPU, which I think is still a bit to much, for being idle.

Expected Behavior

Vmmem not utilizing CPU/RAM until heavy tasks are done

Actual Behavior

Vmmem utilizes high CPU/RAM usage

Diagnostic Logs

No response

[ll931217]

I am having the exact same issue

Windows Build Number

19042.928

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.4.72-microsoft-standard-WSL2

Distro Version

Ubuntu 20.04.2 LTS

Other Software

• Docker Desktop v3.3.1
  • Engine v20.10.5

Repro Steps

Just starting the WSL up and leave your computer on idle.

Whenever WSL starts up, it will use up 2GB of RAM then slowly crawl up to around 6GB. I see in other issues that a lot of the cases are due to having Docker Desktop installed.

After executing wsl --shutdown in PowerShell:

Then starting WSL up:

The above pic is when docker desktop haven't started, which is practically the same as after executing wsl --shutdown, except 100MB difference.

After starting docker desktop:

Expected Behavior

Vmmem not utilizing CPU/RAM until heavy tasks are done

Actual Behavior

Vmmem utilizes high CPU/RAM usage

Diagnostic Logs

No response

[ad-on-is]

I rolled back Windows to the previous build (21359) and vmmem is idleing at 0.5% CPU, under the same conditions.

There's definitely some issue with the new Windows update, maybe WSLg related?

[d1ceward]

I had the same problem since wslg update but adding the ".wslconfig" file in the user root with the option to disable wslg seems to have fixed it (workaround until someone with better understanding can help us).

My .wslconfig file

[wsl2]
guiapplications=false

Distro: Arch linux (from https://github.com/yuk7/ArchWSL)
Windows build number: 21364
WSL 2

[ad-on-is]

My .wslconfig file

[wsl2]
guiapplications=false

Thx!
While this solves the CPU issue, the downside is, it now doesn't allow to run GUI apps.

[ad-on-is]

As per microsoft/wslg#103 they are aware of the problem, and a fix is coming via wsl --update