-
Notifications
You must be signed in to change notification settings - Fork 184
Closed
Labels
Description
Pretty much every time earlyoom triggers, it tends to kill multiple processes within the same second.
Example (running with -p -m 5,2 -s 100,100 -N logger
:
Feb 27 09:34:06 host root[7509]: dialog-warning earlyoom Low memory! Killing process 32194 vmware_vmx
Feb 27 09:34:06 host root[7511]: dialog-warning earlyoom Low memory! Killing process 26773 firefox
Each of these processes would've been enough to free plenty of memory on their own. Wouldn't it be more sensible to minimize damage by killing one process first and waiting just a little to see if the situation improved, before moving on to the next process?
tim77 and vphantom