4 ms·
My experience with that is that 100% CPU can happen if the WSL2 image is using more memory than available, and is then swapping. You should be able to check tha
by rhdunn 2y ago
My experience with that is that 100% CPU can happen if the WSL2 image is using more memory than available, and is then swapping. You should be able to check that by looking at the VmmemWSL process. There's also an option in the WSL config you can specify to limit the amount of memory it can use.
- ohgr 2y agoMachines have 64 gig of memory. vmmem uses only 8. That process just jams at 100% and kills it. You can’t terminate it as it’s not actually a process as such. WSL shutdown does not work.