From: Henrik Storner <henrik@hswn.dk>
To: thomas@habets.pp.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Memory leak in -test9?
Date: 11 Nov 2003 16:29:22 -0000 [thread overview]
Message-ID: <20031111162922.1702.qmail@osiris.hswn.dk> (raw)
In-Reply-To: E1AJahk-00011D-00@reptilian.maxnet.nu
>There seems to be a memory leak in 2.6.0-test9. Before I go on I'll mention
>that the box is running Debian sarge (testing), and the compiler is gcc 3.3.1.
>A lot of memory is used (and eventually it will crash), but very little is in
>cache or buffers. After shutting down zebra, postgresql, snmp and apache this
>is what the system looked like. Notice the Slab-size in /proc/meminfo.
The data from the /proc/slabinfo would be helpful in tracking down
which part of the kernel is using the memory.
Henrik
--
Henrik Storner <henrik@hswn.dk>
next prev parent reply other threads:[~2003-11-11 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 15:36 PROBLEM: Memory leak in -test9? Thomas Habets
2003-11-11 16:29 ` Henrik Storner [this message]
[not found] ` <20031111162734.GA29454@wohnheim.fh-wedel.de>
2003-11-11 17:27 ` Thomas Habets
2003-11-17 10:08 ` Jörn Engel
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=20031111162922.1702.qmail@osiris.hswn.dk \
--to=henrik@hswn.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@habets.pp.se \
/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;
as well as URLs for NNTP newsgroup(s).