> I once locked the entire system so hard neither mouse nor keyboard responded. I did that just the other month on a modern PC using WSL on Win10. Turns out Mc

> I once locked the entire system so hard neither mouse nor keyboard responded. I did that just the other month on a modern PC using WSL on Win10. Turns out McAfee leaks memory like a sieve when faced with WSL, and it leaks it in a way that the memory is never even returned to the OS. Worse, yet, the process using the memory doesn't even show under Task Manager! The memory just appears to disappear. Never noticed at home as I don't run McAfee, but at work had to. It is very quick & easy to fully exhaust memory building even a moderately sized C++ project under WSL. I had hard-lockups several times before I was able to determine the cause, with help from the MS team working on WSL. I had to do a hard restart; there was no way to restart cleanly. Especially problematic when I first ran into it working remotely and RDP'd into my work desktop. Disabling McAfee on my work PC resolved it. (edit: add quote to what I was referring)