Hi Austin, On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote: > On 2016-05-13 08:39, Sebastian Frias wrote: >> >> My point is that it seems to be possible to deal with such conditions in a >> more controlled way, ie: a way that is less random and less abrupt. > There's an option for the OOM-killer to just kill the allocating task instead > of using the scoring heuristic. This is about as deterministic as things can > get though.
By the way, why does it has to "kill" anything in that case? I mean, shouldn't it just tell the allocating task that there's not enough memory by letting malloc return NULL? Best regards, Sebastian
