mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Michael Raskin <a1d23ab4@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc1-mm1+ memory problem
Date: Tue, 21 Nov 2006 11:45:43 -0800	[thread overview]
Message-ID: <20061121114543.817fc06e.akpm@osdl.org> (raw)
In-Reply-To: <4563485B.3050801@mail.ru>

On Tue, 21 Nov 2006 21:41:31 +0300
Michael Raskin <a1d23ab4@mail.ru> wrote:

> Andrew Morton wrote:
> > On Mon, 20 Nov 2006 09:26:29 +0300
> > Michael Raskin <a1d23ab4@mail.ru> wrote:
> > 
> >> Short description: when X is loaded (maybe any heavy application is 
> >> sufficient, but I don't use anything heavy in console), 'free' says used 
> >> memory is growing.
> >>
> Thank you for reply.
> 
> > Monitor /proc/meminfo
> Thanks for advice. I didn't think of it. I should be ashamed.
> 
> Result: mysterious. All fields that grow can not account for even a 
> third part.
> 
> In top I found a situation when 2MB (~half a minute) go to nowhere and 
> no of first 50 processes changes resident memory usage at all. The rest 
> have less than a MB each.
> 
> > If the leak is slab, monitor /proc/slabinfo and /proc/slab_allocators.
> I hope no.
> > /proc/slab_allocators needs CONFIG_DEBUG_SLAB_LEAK.
> > 
> > Thanks.
> > 
> I did a few cat /proc/meminfo. Two of them are here:
> 
> MemTotal:       763532 kB     763532 kB
> MemFree:        445956 kB     430932 kB
> Buffers:         20908 kB      21048 kB
> Cached:          77008 kB      77212 kB
> SwapCached:          0 kB          0 kB
> Active:          65916 kB      66120 kB
> Inactive:        54748 kB      54884 kB
> SwapTotal:     1052216 kB    1052216 kB
> SwapFree:      1052216 kB    1052216 kB
> Dirty:             264 kB        324 kB
> Writeback:           0 kB          0 kB
> AnonPages:       22752 kB      22748 kB
> Mapped:          14616 kB      14628 kB
> Slab:            23108 kB      23088 kB
> SReclaimable:    15360 kB      15364 kB
> SUnreclaim:       7748 kB       7724 kB
> PageTables:       1216 kB       1216 kB
> NFS_Unstable:        0 kB          0 kB
> Bounce:              0 kB          0 kB
> CommitLimit:   1433980 kB    1433980 kB
> Committed_AS:   281456 kB     281448 kB
> VmallocTotal:   262104 kB     262104 kB
> VmallocUsed:      2876 kB       2876 kB
> VmallocChunk:   259028 kB     259028 kB

You lost 15MB and they didn't even turn up on the page LRU.

Can you try to determine exactly which activity causes this to happen?  In
particular, is it due to the X server?  If so, does any particular client
cause it to happen?  Things which use 3d?

  parent reply	other threads:[~2006-11-21 19:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20  6:26 Michael Raskin
2006-11-20 18:18 ` Michael Raskin
2006-11-21  8:37 ` Andrew Morton
     [not found]   ` <4563485B.3050801@mail.ru>
2006-11-21 19:45     ` Andrew Morton [this message]
2006-11-21 21:18       ` Michael Raskin
2006-11-24 13:23 ` Michael Raskin
2006-11-24 23:07   ` Michael Raskin
2006-11-25 19:03     ` Andrew Morton
2006-11-25 21:53       ` Michael Raskin
2006-11-29  4:29 ` 2.6.19-rc6-mm2 is ok (2.6.19-rc1-mm1+ memory problem) Michael Raskin

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=20061121114543.817fc06e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=a1d23ab4@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome