Hello again.
Is Apache::Leak the easiest/best module to use for both detecting AND
allowing us to find the source of a memory leak in mod_perl?
If so, I am not finding any good documentation on its use. I am not a
mod_perl guru and what I've read so far sounds rather involved.
Can someone
Gregory Matthews wrote:
Hello again.
Is Apache::Leak the easiest/best module to use for both detecting AND
allowing us to find the source of a memory leak in mod_perl?
If so, I am not finding any good documentation on its use. I am not a
mod_perl guru and what I've read so far sounds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 20 May 2002 2:47 am, Gregory Matthews wrote:
Hello again.
Is Apache::Leak the easiest/best module to use for both detecting AND
allowing us to find the source of a memory leak in mod_perl?
No - it's a nightmare.
To debug memory leaks
I'm investigating smallish memory leakages in a former CGI script that
is now running live as an Apache::Registry script. I've done the bits
in the famous guide and the SUPPORT document to get a debugging
version of mod_perl going.
According to the error log output, I'm leaking anything between
According to the error log output, I'm leaking anything between 15 and
25 SVs per run of the Apache::Registry script. So, to interpreting the
copious emissions:
new fb1d58 : SV = PVAV(0xffee88)
REFCNT = 1
FLAGS = (PADBUSY,PADMY)
IV = 0
NV = 0
ARRAY = 0x0
ALLOC = 0x0
David Mitchell [EMAIL PROTECTED] writes:
perldoc Devel::Peek and
perldoc perlguts
Ok, done that.
I'm still not clear as to what Apache::Leak is trying to tell
me. Aside from the DESCRIPTION section of the man page saying "Under
Construction" making it seem like you've just as
On 10 Jul 2000, David Hodgkinson wrote:
David Mitchell [EMAIL PROTECTED] writes:
perldoc Devel::Peek and
perldoc perlguts
Ok, done that.
I'm still not clear as to what Apache::Leak is trying to tell
me. Aside from the DESCRIPTION section of the man page saying "
Matt Sergeant [EMAIL PROTECTED] writes:
On 10 Jul 2000, David Hodgkinson wrote:
Sure - looks like you probably don't have any leaks. I tried chasing this
wild goose chase for a while too and ended up just stopping as I wasn't
actually leaking any memory, despite what Devel::Leak tried to
Hi, folks,
I had a question regarding the output of Apache::Leak. I'm testing a
perl module for memory leaks using this module, and I've wrapped my code
inside of a
leak_test {
}
statement. My error_log file (where the output of the leak_test
function goes) ends up with a rather large
