On Mon, Aug 10, 2009 at 4:35 PM, E R wrote:
> What's the best way to find memory leaks in a mod_perl app?
What problem are you trying to solve? Is your app just growing? If
so, that's probably not a leak. You're most likely just using memory.
There are many tips for analyzing and reducing memo
Hi,
What's the best way to find memory leaks in a mod_perl app? I am
trying to use Apache::Leak with mod_perl 1.41
Some notes:
1. My mod_perl app is *HUGE*. Apache::Leak reports over 500,000 SVs. I
think the time it takes to traverse the symbol tables is long enough
to time out my browser (I'm s
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 shar
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 anyw
Chetan Sarva wrote:
> Hey all,
>
> We've got an aging web app running on Apache/1.3.34 (Ubuntu) and
> mod_perl/1.29 which we know has several memory leaks --- apache has
> been crashing of late and we'd like to stop that. For the time being
> we're using Apache::SizeLimit but would like to a
Hey all,
We've got an aging web app running on Apache/1.3.34 (Ubuntu) and
mod_perl/1.29 which we know has several memory leaks --- apache has
been crashing of late and we'd like to stop that. For the time being
we're using Apache::SizeLimit but would like to actually find and fix
the root
