Ideally the core_in filter would allocate the buckets for a single brigade, pass them through the filters, core_out would splash them out and then core_in could theoretically reuse that memory for the next brigade. Obviously it's not how things work at the moment, as the memory is never freed (which could probably be dealt with), but the real problem is that no data will leave the server out before it was completely read in. So httpd always requires at the least the amount of memory that is needed to allocate to store all the incoming data. Which is usually multiplied by at least 2, if there is any transformation applied on that incoming data.
I'm not sure what to advise to Chris, who as a user rightfully thinks that it's 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
