Justin Erenkrantz wrote ..
> On 8/16/06, Jim Gallacher <[EMAIL PROTECTED]> wrote:
> > Actually I don't think apr_pool_destroy() in table_dealloc is actually
> > destroying the pool. I've been poking around in the code and there is
> > something odd going on here.
>
> I would actually love to test
On 8/16/06, Jim Gallacher <[EMAIL PROTECTED]> wrote:
Actually I don't think apr_pool_destroy() in table_dealloc is actually
destroying the pool. I've been poking around in the code and there is
something odd going on here.
I would actually love to test this, but I can't build trunk on Mac OS X.
Alexis Marrero wrote:
> Jim,
>
> This are my results for the memory leak search in apache.table().
>
> The table object creates a memory pool by using apr_pool_create_ex() and
> destroys the pool using apr_pool_destroy(). I added a line in
> MpTable_New() before "return (PyObject*)t" to destroy t
Alexis Marrero wrote:
> Jim,
>
> This are my results for the memory leak search in apache.table().
>
> The table object creates a memory pool by using apr_pool_create_ex() and
> destroys the pool using apr_pool_destroy(). I added a line in
> MpTable_New() before "return (PyObject*)t" to destroy t
Jim,This are my results for the memory leak search in apache.table(). The table object creates a memory pool by using apr_pool_create_ex() and destroys the pool using apr_pool_destroy(). I added a line in MpTable_New() before "return (PyObject*)t" to destroy the pool and ran 1M iterations and I no
