All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonid Kalev <lion@odcnet.com>
To: Rahul Karnik <rahul@genebrew.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Tracking down leaking applications
Date: Sun, 09 Apr 2006 23:37:46 -0700	[thread overview]
Message-ID: <4439FD3A.9060305@odcnet.com> (raw)
In-Reply-To: <b29067a0604090842h3bb11a88re9c175a467763c9f@mail.gmail.com>

Rahul Karnik wrote:

>
>The process killed has been either httpd or cronolog so far. For now,
>I have upgraded to FC4's 2.6.16-1_1069 and added some swap, where
>previously there was none.
>
>Is there a way to:
>- confirm that it is a userspace and not a kernel issue?
>- track down the application that is leaking memory?
>  
>
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:
- the 'ps' utility, to see who eats the memory
- valgrind - an excellent tool for tracking down memory leaks (and other 
bugs, too). Comes with Fedora, but check the Web for a newer version.

Regards,

Leo.

>Thanks for the help,
>Rahul
>--
>Rahul Karnik
>rahul@genebrew.com
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>


  reply	other threads:[~2006-04-10  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09 15:42 Tracking down leaking applications Rahul Karnik
2006-04-10  6:37 ` Leonid Kalev [this message]
2006-04-13 14:12   ` Rahul Karnik
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=4439FD3A.9060305@odcnet.com \
    --to=lion@odcnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rahul@genebrew.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 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.