On Fri, 2008-08-08 at 01:18 +0200, Peter Poeml wrote:
> Anyway, there must be something that I overlook, or there may be other
> circumstances that influence the behaviour (1.2/1.3 difference in pool
> handling??). The patch from trunk fixes the issue for me although I
> can't say why. I can only say for sure that I have a large memleak with
> the current 1.3.x code.
The patch from trunk may work by accident, depending on how
apr_reslist_create() was called and the order of pool destruction.
However, it may create double free situation in some circumstances (this
is what big discussion about pre_cleanups was all about), so it is not
safe.
--
Bojan
|