From: Marcin Szewczyk <Marcin.Szewczyk@wodny.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-kernel@vger.kernel.org, Linux-MM <linux-mm@kvack.org>,
Michal Hocko <mhocko@suse.cz>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
David Rientjes <rientjes@google.com>
Subject: Re: OOM killer kicks in after minutes or never
Date: Thu, 24 Dec 2015 14:14:44 +0100 [thread overview]
Message-ID: <20151224131444.GA3272@orkisz> (raw)
In-Reply-To: <567B9042.9010105@suse.cz>
On Thu, Dec 24, 2015 at 07:27:14AM +0100, Vlastimil Babka wrote:
> +CC so this doesn't get lost
>
> On 21.12.2015 13:35, Marcin Szewczyk wrote:
> > In 2010 I noticed that viewing many GIFs in a row using gpicview renders
> > my Linux unresponsive. There is very little I can do in such a
> > situation. Rarely after some minutes the OOM killer kicks in and saves
> > the day. Nevertheless, usually I end up using Alt+SysRq+B.
Hi,
I thought that due to high throughput of the linux-kernel mailing list
my email will not get a reply if it didn't happen in a day so I allowed
myself to write another email to linux-mm as well as it was suggested to
me on #debian-kernel.
The email is here:
Subject: Exhausting memory makes the system unresponsive but doesn't
invoke OOM killer
Message-ID: <20151223143109.GC3519@orkisz>
http://marc.info/?t=145088116000002&r=1&w=2
I have also updated the description in the repository:
https://github.com/wodny/crasher
Contrary to my original suspicion the OOM killer doesn't need much time
to clean up, it just isn't invoked. Johannes Weiner explained the
probable cause to me in a response in the linux-mm thread.
--
Marcin Szewczyk http://wodny.org
mailto:Marcin.Szewczyk@wodny.borg <- remove b / usuA? b
xmpp:wodny@ubuntu.pl xmpp:wodny@jabster.pl
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-12-24 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151221123557.GE3060@orkisz>
2015-12-24 6:27 ` Vlastimil Babka
2015-12-24 13:14 ` Marcin Szewczyk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151224131444.GA3272@orkisz \
--to=marcin.szewczyk@wodny.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox