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
