From: Rik van Riel <riel@redhat.com>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
werner <w.landgraf@ru.ru>, David Rientjes <rientjes@google.com>,
Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs)
Date: Mon, 09 Apr 2012 11:57:33 -0400 [thread overview]
Message-ID: <4F8306ED.7080405@redhat.com> (raw)
In-Reply-To: <8762d9v10x.fsf@turtle.gmx.de>
On 04/09/2012 03:04 AM, Sven Joachim wrote:
> While I did not experience any crashes or instabilities (yet?), I'm also
> seeing memory leaks. On a system started this morning, with hardly
> anything running:
> where I would expect no more than 50 MB used, 400 MB are actually in use:
>
> ,----
> | $ free
> | total used free shared buffers cached
> | Mem: 3348400 1849712 1498688 0 328960 1119180
> | -/+ buffers/cache: 401572 2946828
> | Swap: 3719040 0 3719040
> `----
Do you see any big memory users in /proc/meminfo or in
/proc/slabinfo?
--
All rights reversed
next prev parent reply other threads:[~2012-04-09 15:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 2:42 v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs) Linus Torvalds
2012-04-09 2:50 ` Andrew Morton
2012-04-09 3:11 ` Linus Torvalds
2012-04-09 7:04 ` Sven Joachim
2012-04-09 15:24 ` Linus Torvalds
2012-04-09 15:43 ` Sven Joachim
2012-04-09 15:57 ` Rik van Riel [this message]
2012-04-09 16:19 ` Sven Joachim
2012-04-09 16:33 ` Rik van Riel
2012-04-09 17:00 ` Pekka Enberg
2012-04-09 17:19 ` Sven Joachim
2012-04-09 17:00 ` Sven Joachim
2012-04-09 17:20 ` Rik van Riel
2012-04-09 10:15 ` David Rientjes
2012-04-09 15:39 ` Linus Torvalds
2012-04-09 21:22 ` David Rientjes
2012-04-09 22:09 ` Linus Torvalds
2012-04-09 23:25 ` David Rientjes
2012-04-09 23:55 ` Linus Torvalds
2012-04-10 0:04 ` David Rientjes
2012-04-14 20:50 ` Srivatsa S. Bhat
2012-04-09 23:56 ` [patch] android, lowmemorykiller: remove task handoff notifier David Rientjes
2012-04-10 1:23 ` Colin Cross
[not found] ` <web-723076709@zbackend1.aha.ru>
[not found] ` <alpine.DEB.2.00.1204091637280.21813@chino.kir.corp.google.com>
[not found] ` <web-723082731@zbackend1.aha.ru>
[not found] ` <alpine.DEB.2.00.1204091707580.21813@chino.kir.corp.google.com>
2012-04-10 7:09 ` v3.4-rc2 out-of-memory problems (was Re: 3.4-rc1 sticks-and-crashs) werner
2012-04-10 7:10 ` werner
2012-04-09 22:13 ` Colin Cross
2012-04-09 22:21 ` Greg Kroah-Hartman
2012-04-09 22:44 ` john stultz
2012-04-09 22:30 ` Linus Torvalds
2012-04-09 23:37 ` David Rientjes
2012-04-10 0:23 ` Colin Cross
2012-04-10 0:32 ` David Rientjes
2012-04-10 1:21 ` Colin Cross
2012-04-10 1:33 ` David Rientjes
2012-04-10 1:37 ` Colin Cross
-- strict thread matches above, loose matches on Subject: below --
2012-04-09 6:52 werner
2012-04-09 7:01 werner
2012-04-10 1:52 werner
2012-04-10 1:51 ` Rik van Riel
2012-04-10 2:13 ` werner
2012-04-10 12:53 werner
2012-04-14 19:38 werner
2012-04-14 19:58 ` Rik van Riel
2012-04-14 21:03 ` Linus Torvalds
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=4F8306ED.7080405@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rientjes@google.com \
--cc=svenjoac@gmx.de \
--cc=torvalds@linux-foundation.org \
--cc=w.landgraf@ru.ru \
/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