-
Notifications
You must be signed in to change notification settings - Fork 797
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
arm64 idle cpu usage very high #9090
Comments
same problem with dev kit 2023. Debian distro |
See here: Same Problem on my Surface Pro X as well as on my Devkit 2023. |
Same issue here with devkit 2023. So either try the previous build 25211, or wait for the fix to make into release channel. |
I can't recommend 25236 in the dev channel at the moment, although I can confirm it fixes the high cpu usage issue on one of my DevKits now - but introduces rendering problems in Edge and other apps. Also, it's a pain to opt out of again (reinstall) so I'm hoping the wsl fixes are moved into the beta channel quick |
To try and fix this issue on my Dev Kit 2023 I installed dev channel build of Windows 25236, but then the machine would not boot so I'm reinstalling Win11 from cloud using reset/restore option ... and that's currently appearing to stuck at 75%. I guess I should have just put up with it and waited until it was fixed in mainstream or beta channels. |
issue was fixed on 22621 with KB5020044. Well done! |
So this is also the case with the Lenovo X13s, high idle CPU around 15%~25%, enough that is drains the battery very fast and makes the laptop sluggish, I'll give 22621 with KB5020044 a go and see if things changed |
I can confirm it's fixed for me also with 22621 in regular Insider now on DevKit 2023
|
Not only that, it often throws a timeout error when booting on matebook e go, and executing |
occasionally after after sleep the vmmemWSL-process gets unresponsive and the jupyter-notebook i launched in it alongside. wsl --shutdown is not working either and the process is not killable via taskmanager. |
Still haven't been able to solve this problem on 22h2. |
Not solved for me. Still very unstable WSL-experience on my Surface Pro 9 (SQ3). But I noticed this: "Fixed an issue causing VmmemWSL to sometimes use an unexpectedly large amount of CPU and lead to freezing on ARM64 devices over time." from https://betawiki.net/wiki/Windows_11_build_25247 - so maybe something is in the works concerning this? I am not in a situation where I can fast forward to 25247 (still on 22623), but maybe there's hope? |
https://github.com/microsoft/WSL/releases/tag/1.1.7 looks promising. |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Version
Microsoft Windows [Version 10.0.22623.875]
WSL Version
Kernel Version
5.15.68.1-microsoft-standard-WSL2
Distro Version
Ubuntu 20.04
Other Software
Project Voltera/Windows Dev Kit 2023 arm64 / aarch64
Repro Steps
Only on Project Voltera/Windows on Arm/Windows DevKit 2023
Start WSL shell
observe CPU usage jumps to 30% total (~80% on 4 of 8 processors)
vmwp.exe
shows high load in process list as wellStop WSL
wsl.exe -t
Ubuntuobserve after ~60s everything back to normal,
vmwp.exe
no longer runningExpected Behavior
On Intel x86_64 Surface Studio 2 no such impact is observable when starting/stopping WSL
Actual Behavior
nothing fails, but CPU/power usage unnecessary high when WSL is in background
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: