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

[pksilen]

Windows Version

10.0.19044.4291

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Just leave your computer unused and at some point you can notice that vmmem process takes close to 100% CPU ranging typically from 95% to 99%. This happens randomly, maybe once a week or once in two weeks or even only once in three weeks. The CPU consumption stays high and makes the computer unresponsive and the CPU consumption of the vmmem process does not seem to settle down. I need to restart my computer or execute wsl --shutdown which will a slow executing command

Expected Behavior

vmmem process CPU consumption stays slow, because no intensive processing is performed on WSL2.

Actual Behavior

Vmmem process takes close to 100% pf CPU and the CPU consumption does not seem settle down by itself.

Diagnostic Logs

This problem is not specific to a certain WSL2 version. This has been an active issue for at least one and half years if not longer.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL stops responding and vmmem spikes CPU to 100% (#9592), similarity score: 0.84
• WSL high CPU usage and hangs all requests after some sleep-resume or hibernate-resume cycles (#9855), similarity score: 0.82
• Vmmem high CPU usage (#6982), similarity score: 0.82

Closed similar issues:

• WSL: vmmem shows 99% CPU - eventually crashes windows 10 (#8991), similarity score: 0.86
• Vmmem suddenly using too much CPU when idle (#6837), similarity score: 0.83

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL stops responding and vmmem spikes CPU to 100% (#9592), similarity score: 0.84
• WSL high CPU usage and hangs all requests after some sleep-resume or hibernate-resume cycles (#9855), similarity score: 0.82
• Vmmem high CPU usage (#6982), similarity score: 0.82

Closed similar issues:

• WSL: vmmem shows 99% CPU - eventually crashes windows 10 (#8991), similarity score: 0.86
• Vmmem suddenly using too much CPU when idle (#6837), similarity score: 0.84

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!