All of lore.kernel.org
 help / color / mirror / Atom feed
From: Skip Gaede <sgaede@attbi.com>
To: linux-kernel@vger.kernel.org
Subject: Memory leak
Date: Wed, 19 Jun 2002 22:24:03 -0400	[thread overview]
Message-ID: <200206192224.03785.sgaede@attbi.com> (raw)

Folks,

I'm looking for a recipe on how to track where my memory is 
disappearing to. I am running kernel 2.4.19-pre10-ben0, 
patched for the nubus-pmac platform. I have 40 MB RAM and a 
100 MB swap file on the local hard disk.

I am using the MkLinux booter and the kernel with an initrd. 
During the first init, I get an IP address and the path to 
the NFS root. I then do a pivot-root, and run the XFree86 
Server -query 192.168.0.1, where I do an autologon, and 
start up KDE 3.0.1 and Mozilla 1.0 running Choffman's 
browser buster. I also am running the snmp daemon, so I can 
monitor memory use from my server with a perl script.

When first booted, the kernel takes about 16 MB of memory, 
and after starting the X server, I have about 2000k 
available physical memory, and no swap file useage. Over 
the next 7 hours, I eat up about 20 MB of swap file, and at 
some point the available physical memory drops down to 
about 150k for about an hour and then the system locks up.
During the same period of time, I can monitor memory use on 
the client on another console, and the amount of memory 
allocated to each process remains fairly stable.

I'd like to understand what's going on. Can someone suggest 
what data I ought to be collecting, or perhaps some 
parameters I can tweak to modify the behavior?

Thanks,
Skip

             reply	other threads:[~2002-06-20  2:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  2:24 Skip Gaede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20  7:52 Memory leak Skip Gaede
2002-06-22  2:22 ` Skip Gaede
2002-06-20 15:06 diekema_jon
2002-08-26 19:01 Aleksandar Kacanski
2002-08-26 19:29 ` Richard B. Johnson
2002-08-26 19:44   ` george anzinger
2002-08-26 20:05     ` Richard B. Johnson
     [not found]     ` <Pine.LNX.3.95.1020826155614.6481A-100000@chaos.analogic.co m>
2002-08-27  5:44       ` Mike Galbraith
2002-08-27  3:43   ` jw schultz
2003-03-09 16:46 matsunaga
2003-03-09 17:37 ` Charles Manning
2003-03-09 19:10 ` Thomas Gleixner
2003-03-09 23:10   ` matsunaga
2003-03-10 14:53     ` Thomas Gleixner
2003-03-10 14:14       ` David Woodhouse
2003-03-10 15:48         ` matsunaga
2003-03-10 16:02           ` David Woodhouse
2003-03-10 16:26             ` matsunaga
2003-03-10 17:04               ` David Woodhouse
2003-03-11 15:52                 ` matsunaga
2003-03-11 18:39                   ` Thomas Gleixner
2003-03-10 15:36       ` matsunaga
2003-03-11 17:50 ` David Woodhouse
2003-03-12 19:50 Memory Leak Aman
2003-03-12 20:29 ` Matt Porter
2008-04-09 13:54 Memory leak hinko.kocevar
2026-01-19  5:14 [PATCH v26 2/2] status: add status.compareBranches config for multiple branch comparisons Jeff King
2026-01-20  9:49 ` Memory leak Harald Nordgren
2026-01-20 13:22   ` Harald Nordgren
2026-01-20 21:42     ` Junio C Hamano
2026-01-21 18:47       ` Junio C Hamano
2026-01-21 20:49         ` Jeff King
2026-01-22 15:03         ` Harald Nordgren
2026-01-22 18:19           ` Junio C Hamano

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=200206192224.03785.sgaede@attbi.com \
    --to=sgaede@attbi.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 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.