3 ms·
Until it breaks. I watched a colleague have to reinstall his laptop the other day because whenever he opened a WSL terminal, nothing happened and it banged the
by ohgr 2y ago
Until it breaks. I watched a colleague have to reinstall his laptop the other day because whenever he opened a WSL terminal, nothing happened and it banged the CPU at 100% and wouldn’t even shut down.
Have seen that a few times from different people.
- rhdunn 2y agoMy 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.
- StableAlkyne 2y agoNever heard of that happening myself, and I've been on a few teams that used it going back to the WSL1 days. Not saying that it didn't, either. Just that it might not be a widespread issue
- deleted 2y ago[deleted]