--- Joe Lewis <[EMAIL PROTECTED]> wrote:
> Your buckets can still be created using the
> request->pool . My created
> buckets in my output filter are done that way. Have
> you tried it? You
> still use the request->connection->bucket_alloc for
> the other parameter,
> but the request->pool for
John Zhang wrote:
> --- Ray Morris <[EMAIL PROTECTED]> wrote:
>
>
>>> I am using the apr_* functions to allocate
>>> memory (most of the time from the request->pool).
>>>
>>If there are few places where you allocate from
>> othr than the reqquest pool, I'd look at those
>> first.
>>
I am using the apr_* functions to allocate
memory (most of the time from the request->pool).
If there are few places where you allocate from
othr than the reqquest pool, I'd look at those first.
--
Ray B. Morris
[EMAIL PROTECTED]
Strongbox - The next generation in site security:
http://www.be
--- Eric Covener <[EMAIL PROTECTED]> wrote:
>
> It should level out as each thread in the process
> has had a chance to
> run and allocate some memory for a range of
> requests. MaxMemFree can
> be used to return the heap memory that would
> otherwise be used by
> subsequent requests on that thr
On Dec 14, 2007 6:05 PM, John Zhang <[EMAIL PROTECTED]> wrote:
> When my module processes requests, I see a consistent
> memory increase. It is like the memories were never
> released. I am using the apr_* functions to allocate
> memory (most of the time from the request->pool). My
> understandi
