From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: how to find out it's a memory leak?
Date: Mon, 22 Nov 2004 00:05:52 +0100 [thread overview]
Message-ID: <41A11F50.6060501@g-house.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi list,
during the last weeks i've encounterd some OOM situation here on my little
server machine. that happened with some 2.6.9 and 2.6.10 kernels but i
never found out what the reason was. the machine was running for 2 or 3
weeks and constantly taking up more and more swap until the OOM killer did
his job and killed some task. i decided to reboot then, once i *had* to
reboot because the machine has locked up.
so i suspect a "memory leak" somewhere. knowing nothing about VM and
knowing the term "memory leak" only from hearsay, i just want to know
1) does a memory leak always occur in kernel space? or could some
userspace application take up more and more swapspace too?
2) where can i look for the process to blame?
i've already thought about it and i really think a userspace app can also
be the bad one here, but "top" and "ps" won't tell me who's to blame.
perhaps somewhere under /proc, but i don't know where. can someone tell me
where to look for?
currently i'm running 2.6.10-rc1-bk19 and 436MB swapspace is already used.
that's not "normal" for this machine and i can from daily "free -m"
outputs that more and more swapspace is used - but i don't know by what!
thanks,
Christian.
- --
BOFH excuse #227:
Fatal error right in front of screen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBoR9Q+A7rjkF8z0wRAiJ6AJ9B1xGegsOUaZ5N0ux2sG6CABAwKQCeO4AF
3PaLcQJM48qOksTFBIKch/k=
=zC0i
-----END PGP SIGNATURE-----
next reply other threads:[~2004-11-21 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 23:05 Christian Kujau [this message]
2004-11-22 2:22 ` Andreas Dilger
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=41A11F50.6060501@g-house.de \
--to=evil@g-house.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
Powered by JetHome