public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Rieke <andreas.rieke@isl.de>
To: linux-kernel@vger.kernel.org
Subject: Kernel memory leak?
Date: Mon, 17 Jul 2006 18:53:49 +0200	[thread overview]
Message-ID: <44BBC09D.5060409@isl.de> (raw)

Hi,

after booting a machine, it runs well using about 300 M of 1 G physical
RAM. However, the remaining RAM decreases day by day, and after 2 or 3
weeks, the machine crashes because swapping takes too much time.
However, all processes together take about 250 MBytes according to ps,
thus I assume that the kernel takes the rest. free tells me in fact that
much swap space is used an nearly no physical RAM is left.

This behaviour has been seen on Red Hat Enterprise Linux 3 with a 2.4
kernel and on SuSE Linux 10 with a 2.6.13-15-default kernel. There are
no unusual things running on the machine, the main application is an
apache web server with a PostgreSQL database.

Is there any kernel support to detect where the memory has gone?
Is any kind of memory eating virus or worm known?
Is it possible that processes request memory which is NOT considered in
/proc or in the procps tools?
Is it possible that processes are invisible in /proc or in the procps tools?

Thanks in advance,

Andreas

             reply	other threads:[~2006-07-17 16:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 16:53 Andreas Rieke [this message]
2006-07-17 18:28 ` Kernel memory leak? Michal Piotrowski
  -- strict thread matches above, loose matches on Subject: below --
2002-10-10 18:09 kernel " Dow, Benjamin
2002-10-10 16:31 Manfred Spraul
2002-10-10 14:32 Dow, Benjamin
2002-10-08 18:16 Dow, Benjamin
2002-10-08 22:54 ` Pavel Machek
2002-10-11  8:54   ` Nicholas Hockey
2002-10-11  8:58   ` Nicholas Hockey
2002-10-07 21:58 Dow, Benjamin

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=44BBC09D.5060409@isl.de \
    --to=andreas.rieke@isl.de \
    --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