Re: Hashtable data freed before pool cleanup

On Thu, Jan 7, 2010 at 7:26 AM, Ruediger Pluem <rpluem_at_apache.org> wrote:
> This sounds like a valid point.

Yup. My fault -- sorry!

> I would propose to revert r817810 / r817809 (for 1.3.x / 1.4.x) and only
> keep r817806 (trunk). Graham?
> IMHO we can backport this again later if the problem is sorted out in trunk.

Well, the suggested fix of using a sibling pool to the hash table's
pool would work, I think -- I'd be happy to prepare patches to
implement that. But I also wouldn't object to just backing out the
change from the stable branches.

I wonder if, for APR2, it might make sense to change the pool cleanup
behavior so that cleanup handlers for sub-pools are invoked, then for
parent pools up the hierarchy, and only after all cleanup handlers are
invoked is any memory actually reclaimed.

Neil
Received on 2010-01-07 20:30:24 CET