All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel20120920@schottelius.org>
To: David Rientjes <rientjes@google.com>
Cc: Nico Schottelius <nico-kernel20120920@schottelius.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Out of memory on 3.5 kernels
Date: Thu, 20 Sep 2012 09:32:45 +0200	[thread overview]
Message-ID: <20120920073245.GA1327@schottelius.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1209192351440.30029@chino.kir.corp.google.com>

Hey David,

David Rientjes [Wed, Sep 19, 2012 at 11:54:54PM -0700]:
> On Thu, 20 Sep 2012, Nico Schottelius wrote:
> 
> > for some time the slab usage is quite high (~3.2 GiB) and whenever I try
> > to do a backup with ccollect (which is using rsync), a lot of processes
> > (like chromium) are being killed over night.
> > 
> 
> Yeah, over 81% of your memory is consumed by slab and that doesn't shrink 
> over the duration of the log you posted.  It would be interesting to see 
> if there was a leak somewhere: try looking at slabtop and determining if 
> you have a cache using an egregious amount of memory;

I already had to reboot, because no now process was starting / only
starting extremly slowly.

> if there aren't any 
> clear winners, then we'll still see what is hogging most of your memory 
> and see how it compares to 3.4.2.  You can also check if there is a leak 
> using kmemleak, but this requires a reboot (see 
> Documentation/kmemleak.txt).

I'll have a look at this one after the next reboot; I also have to
update to a recent kernel and enable CONFIG_DEBUG_KMEMLEAK, which is
missing in Archlinux' kernel.

Thanks for the pointers, it can only take a day until I have this
problem again - will then follow up this mail.

Cheers,

Nico

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

  reply	other threads:[~2012-09-20  7:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  6:02 Out of memory on 3.5 kernels Nico Schottelius
2012-09-20  6:54 ` David Rientjes
2012-09-20  7:32   ` Nico Schottelius [this message]
2012-09-20  7:44     ` Arend van Spriel
2012-09-20  8:21       ` Nico Schottelius
2012-09-20 12:12       ` Nico Schottelius
  -- strict thread matches above, loose matches on Subject: below --
2012-09-20 13:52 Arend van Spriel
2012-09-21 19:49 ` Nico Schottelius
2012-09-24 22:43   ` David Rientjes
2012-09-25 15:07     ` Dave Kleikamp
2012-09-26  6:03       ` Nico Schottelius
2012-09-26  6:06     ` Nico Schottelius
2012-09-26  8:57       ` Nico Schottelius
2012-09-27  5:52         ` Nico Schottelius
2012-10-03 21:23           ` Nico Schottelius
2012-10-05 15:48             ` Valdis.Kletnieks
2012-10-05 17:51               ` Nico Schottelius
2012-10-30 10:35                 ` Nico Schottelius
2012-11-21 22:37                   ` Dave Kleikamp

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=20120920073245.GA1327@schottelius.org \
    --to=nico-kernel20120920@schottelius.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.