valgrind won't help because apache doesn't free the memory from it's pool, so valgrind doesn't catch any.
you look for setting the debug level such that you get to track the pool growth. there is a global pool, there is pool per connection and there is a pool per request. -thanks harish On Wed, Feb 17, 2010 at 1:06 AM, Kevac Marko <[email protected]> wrote: > On Tue, Feb 16, 2010 at 2:10 PM, harish kulkarni <[email protected]> > wrote: > > > http://harishvk27.wordpress.com/2008/11/05/fixing-memory-leak-in-apache-mod_proxy/ > > Thank you. But I am surprised that no one uses valgrind. > > -- > Marko Kevac > Sent from Moscow, Mow, Russia >
