Yes, it grows in 4k chunks just about every page reload. And when I hit it from a test script just doing a GET to the exact same page, it grows much faster (still at 4k rate), but you can see the proc size grow infront of your eyes!

And again, just for clarity, this is happening on a statically compiled mod_perl and DSO mod_perl. But DOES NOT happen when I DSO a C handler on this Linux machine nor on a FreeBSD machine with static mod_perl.

Any ideas on how to identify the cause of the leak?

Perrin Harkins <[EMAIL PROTECTED]> wrote:
On Wed, 2006-06-07 at 13:58 -0700, john doe wrote:
> It was written as a handler. I did not even send the constants, just
> a direct 200. (Altough I tried return OK, too).

This doesn't look like it should grow. It never stopped growing? You
could hit it all day and it would increase? (Seeing an increase every
time would actually be quite strange, since Perl allocates memory in
chunks.)

- Perrin


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Reply via email to