earlyoom [OPTION]...
The oom-killer generally has a bad reputation among Linux users. One may have to sit in front of an unresponsive system, listening to the grinding disk for minutes, and press the reset button and get back to what was doing quickly after running out of patience.
earlyoom checks the amount of available memory and free swap 10 times a second. If both are below 10%, it will kill the largest process. The percentage value is configurable via command line arguments.
Earlyoom does not use echo f > /proc/sysrq-trigger because the Chrome people made their browser always be the first (innocent!) victim by setting oom_score_adj very high. Instead, earlyoom finds out itself by reading through /proc/*/status (actually /proc/*/statm , which contains the same information but is easier to parse programmatically).
Additionally, in recent kernels (tested on 4.0.5), triggering the kernel oom killer manually may not work at all. That is, it may only free some graphics memory (that will be allocated immediately again) and not actually kill any process.
About 0.6MB RSS. All memory is locked using mlockall() to make sure earlyoom does not slow down in low memory situations.
The author of earlyoom is Jakob Unterwurzacher.
This manual page was written by Yangfl, for the Debian project (and may be used by others).