4 ms·
systemd-oomd is also default since Ubuntu 22.04. I remember it vividly because it effectively kept killing X when RAM filled up instead of sanely killing the pr
by mxmlnkn 3y ago
systemd-oomd is also default since Ubuntu 22.04. I remember it vividly because it effectively kept killing X when RAM filled up instead of sanely killing the process that last filled up the RAM, which is either gcc or firefox in my case. Absolutely user-unfriendly default configuration. I removed it and reinstalled earlyoom, which I have been using for years with a suitable configuration. I can only concur, RAM behavior isn't user-friendly on Ubuntu.
- konstantinua00 3y agoI second the earlyoom recomendation it's a lifesaver
- khimaros 3y agopersonally, i run my systems without swap, and kernel OOM behavior has been adequate.
- pxtail 3y agoThank you for mentioning earlyoom - I'll install and try it because current behavior of total, complete lockup without ability to do anything besides reset with the hardware button infuriates me unbelievably. I really don't comprehend how something like this is possible and default behavior in 2023 in OS marketed as 'desktop' and 'casual/user friendly'
- mhitza 3y agoHad the same experience in the past with systemd-oomd, nowadays it does a better job at killing greedy processes than the entire user slice/scope.