[mod_python] mod_python 3.3.1 memory leak?

Now, the python streamer only issue one flush about every 30 frames, the
memory usage grows very slow:)

Maybe Apache is too complicated for me, its default output filters requires
the buckets and brigades.

apr_brigade_create does actually do the pool allocation:

APU_DECLARE(apr_bucket_brigade *) apr_brigade_create(apr_pool_t *p,
                                                     apr_bucket_alloc_t
*list)
{
    apr_bucket_brigade *b;

    b = apr_palloc(p, sizeof(*b));
    b->p = p;
    b->bucket_alloc = list;

    APR_RING_INIT(&b->list, apr_bucket, link);

    apr_pool_cleanup_register(b->p, b, brigade_cleanup,
apr_pool_cleanup_null);
    return b;
}



On 7/4/07, Graham Dumpleton <graham.dumpleton at gmail.com> wrote:
>
> On 04/07/07, Graham Dumpleton <graham.dumpleton at gmail.com> wrote:
> > 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.
>
> Okay, I'm confused now. The bucket functions aren't supposed to be
> allocating memory out of the resource pool.
>
> /**
> * Create a new bucket brigade.  The bucket brigade is originally empty.
> * @param p The pool to associate with the brigade.  Data is not allocated
> out
> *          of the pool, but a cleanup is registered.
> * @param list The bucket allocator to use
> * @return The empty bucket brigade
> */
> APU_DECLARE(apr_bucket_brigade *) apr_brigade_create(apr_pool_t *p,
>                                                     apr_bucket_alloc_t
> *list);
>
> Ie., it takes buckets from a bucket list, to which buckets are
> returned for reuse when the bucket brigade is no longer needed at the
> completion of the operation.
>
> The only reason the request pool is required is so that the bucket
> brigade can be cleaned up automatically if the code forgets to
> explicitly destroy it before the request is over.
>
> So, looks like I have some more research to do to understand all this. :-(
>
> Graham
>



-- 
truly yours
ice
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20070704/09065355/attachment.html