From: "Rahul Karnik" <rahul@genebrew.com>
To: "Leonid Kalev" <lion@odcnet.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Tracking down leaking applications
Date: Thu, 13 Apr 2006 10:12:53 -0400 [thread overview]
Message-ID: <b29067a0604130712r275c3f0bndd1cc928415b3255@mail.gmail.com> (raw)
In-Reply-To: <4439FD3A.9060305@odcnet.com>
On 4/10/06, Leonid Kalev <lion@odcnet.com> wrote:
> This seems a bit off-topic for LKML, because you should *always* check
> user-space for memory leaks before blaming the kernel. A few things that
> can help you with your questions:
Not blaming the kernel yet, just wondering if it can help me track
down the offending app.
> - the 'ps' utility, to see who eats the memory
Well, httpd is at the top of the list, as it should be. What I cannot
tell is if the processes are leaking memory, or if all is well.
> - valgrind - an excellent tool for tracking down memory leaks (and other
> bugs, too). Comes with Fedora, but check the Web for a newer version.
I will try valgrind on the web application.
Thanks for the help!
-Rahul
--
Rahul Karnik
rahul@genebrew.com
next prev parent reply other threads:[~2006-04-13 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 15:42 Rahul Karnik
2006-04-10 6:37 ` Leonid Kalev
2006-04-13 14:12 ` Rahul Karnik [this message]
2006-04-13 10:30 ` Alan Cox
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=b29067a0604130712r275c3f0bndd1cc928415b3255@mail.gmail.com \
--to=rahul@genebrew.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lion@odcnet.com \
/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®