Perrin Harkins wrote: [...] >> My question is this...can I run my application using this purified perl >> under mod_perl to track down potential memory leaks and other problems? > > > You probably don't have any memory leaks. Most things that people refer > to as leaks are just normal growth. A leak is when an area of memory > gets "lost" because the program that allocated it forgets to free it.
or cannot free it because of the closure or a circular reference, which seems to be the case with the bug in Apache::Request reported by Dave Rolsky. [...] > A number of the most common sources of memory growth are explained in > the guide: > >http://perl.apache.org/docs/1.0/guide/performance.html#Improving_Performance_by_Prevention > Plus Apache::Leak, whose reports should be carefully analyzed because not everything that it reports as a leak is actually a leak: http://perl.apache.org/docs/1.0/guide/debug.html#How_can_I_find_out_if_a_mod_perl_code_has_a_memory_leak __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
