> I looked through the libxml2 sources a little bit but couldn't
> immediately find the problem. I'm fairly confident though that
> this could be reproduced outside Postgres, by replicating the sequence
> of libxml2 calls we make in xpath(). The next step should probably be
> to build a reproducer program and submit it to the libxml authors,
> or maybe run it under a debugging malloc package that could help
> identify where the leak is. Anyone want to do that?
Ugh, I'd love to give that a shot but that is a bit outside my comfort zone.
-- m@
