Graham Dumpleton
graham.dumpleton at gmail.com
Tue Jul 3 19:04:14 EDT 2007
On 03/07/07, yubing <trueice at gmail.com> wrote: > Anyhow, it's clear that ap_rflush is the root cause of this memory leak, > maybe we should find a new API for this (maybe we should also add a new > method to the request_object ). It is not just ap_rflush() but also ap_rwrite(), as it is also using the request pool. To avoid the problem would mean creating a separate pool just for the one operation and for the buckets to be allocated from that, with the pool destroyed at the end of the call. Unfortunately it isn't perhaps quite as simple as that though. This is because one can only use a separate pool if you know the buckets would be used up and no longer required after the call. When doing a flush this may be the case, but need to check. Definitely not the case if not doing a flush though. Graham
|