It is explained here that the OOM-Killer can be configured via
overcommit_memory and that:
- 2 = no overcommit. Allocations fail if asking too much.
- 0, 1 = overcommit (heuristically or always). Kill some process(es) based on some heuristics when too much memory is actually accessed.
Now, I may completely misunderstand that, but why isn't there an option (or why isn't it the default) to kill the very process that actually tries to access too much memory it allocated?