It's 2015, and OOM handling still sucks

[Ian Malone]

On 1 December 2015 at 18:47, Neal Becker <ndbecker2 at gmail.com> wrote:
> Ian Malone wrote:
>
>> On 1 December 2015 at 15:19, Neal Becker <ndbecker2 at gmail.com> wrote:
>>> I have a pretty nice workstation, with 8 cores and 32G RAM.
>>>
>>> A stupid little python program just killed it by consuming all the
>>> memory, driving it into swapping hell.
>>>
>>> I couldn't even ssh into it - I started up ssh and went for coffee.  On
>>> return I still didn't have a prompt.  Had to power cycle it.
>>>

>> Maybe one for the devel list where they can do something about it. I
>> haven't actually checked what the current Fedora policies are, since
>> at work I use RHEL. I'd have thought the oom killer would get this.
>> Really taking out all the memory with no swap available seems more
>> likely to kill a system, possibly memory use can expand too fast, but
>> on systems with some swap I've rarely seen things get to the point you
>> can't get a virtual terminal up.

> cat /proc/meminfo
<snip>

Well, first time for everything. Can you share what the program was?
There are examples on stackoverflow which intentionally do this kind
of thing, but doing it without meaning to is impressive. For my own
interest, is your swap on SSD?

-- 
imalone
http://ibmalone.blogspot.co.uk