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

I didn't do anything in WSL2 Arm64, but in Windows Task Manager, it shows that "Virtual Machine Worker Processes" and "System" occupy about 30% of the CPU. What should I do #11650

Closed
1 of 2 tasks
AlexanderDash opened this issue Jun 4, 2024 · 2 comments

Comments

@AlexanderDash
Copy link

Windows Version

10.0.22000.2538

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

CPU is Snapdragon 8cx Gen3
Windows11 Arm64 21H2 (22000.2538)

WSLg version: 1.0.60

MSRDC version: 1.2.5105

Direct3D version: 1.611.1-81528511

DXCore version: 10.0.25131-1002-220531-1700. rs onecore base2 hyp

Repro Steps

Open Ubuntu and do nothing, occupying 30% CPU
2024-06-04 16 09 17
When I wsl -- shutdown, it doesn't take up my CPU anymore

Expected Behavior

occupying 2% CPU,Make it right,I didn't do anything, why is it taking up my CPU

Actual Behavior

Open Ubuntu and do nothing, occupying 30% CPU

Diagnostic Logs

No response

Copy link

github-actions bot commented Jun 4, 2024

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 [email protected] 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:

Closed similar issues:

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

@AlexanderDash
Copy link
Author

After updating Windows 11, it was resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant