Hi, David Turner wrote:
On Fri, 2007-04-13 at 08:44 +0200, Stefan Behnel wrote:
David Turner wrote:
I'm trying to write some code that uses lxml, and I run into a weird memory error.
Unfortunately, I can't seem to create a small testcase. So this bug report probably won't be very useful. Running valgrind shows a couple of memory errors. The first is in xmlFreeNode, when it attempts to get the dict from a doc that has been freed. The node in question is created at line 327 of tasklist.py in transcluder -- but the error comes later, during garbage collection.
Could you send me the valgrind log? bzip2 is fine.
It's small, so I attached it here.
sadly, that doesn't tell me much. Also, I can't easily get your example to run, so I won't be able to test it. You appear to run a patched version of libxml2 (2.6.17, you said) as the line numbers from your valgrind trace don't match the sources. I can see that you are using iteration and you seem to be using threads. Threading is most likely required to reproduce this bug and the iteration is likely related, but I can't tell what happens here without reproducing it. Stefan