[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Finding memory leaks
- Subject: Re: Finding memory leaks
- Date: Wed, 24 Oct 2007 10:15:22 -0700
- From: "Manoj Bist" <suppressed>
The following always works for me:
Run apache2(pre fork) with '-X' option under valgrind:
In my system it looks something like this:
valgrind --leak-check=full /usr/sbin/apache2 -X
If you are using any 'XS' based perl modules, it would show memory leaks/errors, if any in any of the loaded shared libs.
On 10/24/07, Chetan Sarva
<suppressed> wrote:
On Oct 24, 2007, at 3:59 AM, Philippe M. Chiasson wrote:
> Have you tried Apache::Leak?
>
> http://search.cpan.org/~gozer/mod_perl-1.30/Leak/Leak.pm
Everything I've read about Apache::Leak says it points out lots of
false positives and can be a huge waste of time. Maybe I'll give it a
try anyway. I've got time to waste.
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.