Jake Weinstein
Jake Weinstein
Hi @OneBlue I did just reproduce the issue on 1.1.2, but unfortunately, wsl.exe --debug-shell is currently just freezing whether I run it from PowerShell or cmd. wsl --shutdown also does...
Somewhat related issue today. WSL is still responsive, but vmmem is using 7,828 MB of RAM. This time, I was extracting images, which is a multi-gigabyte operation. It's been several...
Same high CPU issue today, I am not running much in WSL, but noticed my fans making a lot of noise, checked Task Manager, Vmmem is above 80% CPU. Debug...
Got it again just now, but again I cannot launch the WSL debug shell to capture the processes @OneBlue
Happened again today, I did not even touch it this time, it was just open in the background from yesterday.
I just resumed my computer after rebooting. I heard my fans get loud. WSL is not running at all, but Vmmem is at 80% CPU. I still can't open the...
Had the lockup yesterday. Right now, Vmmem is at 23.7% CPU, fans are loud, but it is still responsive. This does not add up anywhere near 23.7% CPU. root@(none) [...
Full lock up again
@rkm thank you for that command! Restarting every time was really annoying but I never found any commands that had the permissions they needed.
Just had the lockup on 1.2.0.