4 ms·
I don't understand why this issue still persists on linux. As far as I can tell all earlyoom needs to do is kill the process that has eaten the most memory in t
by jaggirs 4y ago
I don't understand why this issue still persists on linux. As far as I can tell all earlyoom needs to do is kill the process that has eaten the most memory in the last minute or so. On windows this issue is non-existent.
- viraptor 4y agoIt's not that simple. Imagine something leaking memory running on parallel with something bursty. For example your browser leaks, but you run a big grep|sort in the background. Or have some GC runtime which allocates in batches and just decided it needs another chunk to manage. On Windows you don't have oom at all because it trades that solution for just swapping forever until either you can't do anything or manage to kill the right app yourself.
- gmokki 4y agoI think it has now been finally fixed in Linux 6.1: https://www.phoronix.com/news/Linux-MGLRU-v9-Promising https://www.phoronix.com/news/Linux-MGLRU-v9-Promising People have reported that their machines with small amount of RAM are now fully usable where previously the system become completely unresponsive when swapping started.