Hi Stas,

Got rather a shock this morning when I discovered twenty odd emails in
my Inbox!! I can see why open source development moves so fast ;)

The version in CVS looks good. It consumes very little memory now,
starts off at 0.6%. I think there is still a small leak, it creaps up
very slowly at about 0.1% every 5 minutes. I can see this being very
difficult to track...

If you want me to run any tests, I would be happy to do so.

Thank you for your hard work and effort over the past few days, it is
very much appreciated!

---
Regards,
Chris Pringle

UK PSG
Hewlett-Packard, Bristol
Tel: +44 117 31 29664


> -----Original Message-----
> From: Stas Bekman [mailto:[EMAIL PROTECTED] 
> Sent: 11 December 2003 07:44
> Cc: Pringle, Chris (HP-PSG); [EMAIL PROTECTED]
> Subject: Re: [mp2] Memory Leak
> 
> 
> Stas Bekman wrote:
> > Pringle, Chris (HP-PSG) wrote:
> > 
> >> Stas,
> >>
> >> I tried the latest version this morning, and it doesn't appear to 
> >> have made a great deal of difference. I'm not sure whether it 
> >> consumes memory as fast, however, as you said, there are leaks 
> >> elsewhere. The following code reproduces it.
> 
> Chris, please try the current cvs. This time it should be all 
> clean. I hope.
> 
> I've switched memory allocation from pools to plain malloc, 
> so the memory is 
> freed at the end of each filter invocation. what was 
> happening previously is 
> that memory was allocated from pools and freed at the end of 
> request, causing 
> huge memory demands).
> 
> __________________________________________________________________
> 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
> 
> 

--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html

Reply via email to