mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mru@users.sourceforge.net (Måns Rullgård)
To: Andrew Rodland <arodland@noln.com>
Cc: mru@users.sourceforge.net (M), linux-kernel@vger.kernel.org
Subject: Re: memory leak?
Date: 21 Jul 2002 16:19:35 +0200	[thread overview]
Message-ID: <yw1x1y9xups8.fsf@gladiusit.e.kth.se> (raw)
In-Reply-To: Andrew Rodland's message of "Mon, 22 Jul 2002 10:08:40 -0400"

Andrew Rodland <arodland@noln.com> writes:

> On 21 Jul 2002 16:00:09 +0200
> mru@users.sourceforge.net (M) wrote:
> 
> > 
> > I noticed that doing lots or file accesses causes the used memory to
> > increase, *after* subtracting buffers/cache. Here is an example:
> > 
> > $ free
> >              total       used       free     shared    buffers    
> >              cached
> > Mem:        773776      30024     743752          0       1992     
> > 10424-/+ buffers/cache:      17608     756168
> > Swap:        81904          0      81904
> > $ du > /dev/null
> > $ free
> >              total       used       free     shared    buffers    
> >              cached
> > Mem:        773776      78008     695768          0      26328     
> > 10472-/+ buffers/cache:      41208     732568
> > Swap:        81904          0      81904
> > 
> > Here 24 MB of memory have been used up. Repeating the du seems to have
> > little effect. This directory has ~3200 subdirs and 13400 files.
> > 
> > After a few hours use about 200 MB are used, apperently for
> > nothing. Killing all processed and unmounting file systems doesn't
> > help.
> > 
> > Is this a memory leak? I get the same results with ext2, ext3,
> > reiserfs and nfs.
> 
> wow!
> I've been seeing this, too, but I thought I was just reading something
> wrong. Especially after my nightly cron jobs (which involve a 'find
> /') run, I'll often find myself with 80% of physical RAM used, and
> nobody (as far as 'top' can see) using it. You didn't specify which
> kernel you're using, but I'm running 2.4.19-rc1-ac1 plus some patches,
> and I've seen it since at least about pre9-ac*. I might try to narrow it
> down more if it could be useful.

I forgot to mention the kernel version. It's 2.4.19-rc3. It's been
going on a while, though, before I took the time start looking for it.

-- 
Måns Rullgård
mru@users.sf.net

  reply	other threads:[~2002-07-21 14:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 14:00 Måns Rullgård
2002-07-21 14:19 ` Rik van Riel
2002-07-21 14:23   ` Måns Rullgård
2002-07-21 16:33     ` Alan Cox
2002-07-21 20:48       ` Måns Rullgård
2002-07-21 21:08         ` Rik van Riel
2002-07-30 16:08           ` Bill Davidsen
2002-07-30 16:43             ` Rik van Riel
2002-07-22 14:08 ` Andrew Rodland
2002-07-21 14:19   ` Måns Rullgård [this message]
2002-07-21 14:20   ` Martin Josefsson
2002-07-21 22:27     ` Stephan Maciej
2002-07-22 14:26     ` Andrew Rodland
2002-07-21 14:50       ` Rik van Riel

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=yw1x1y9xups8.fsf@gladiusit.e.kth.se \
    --to=mru@users.sourceforge.net \
    --cc=arodland@noln.com \
    --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

all inboxes | Powered by JetHome®