On Thu, 2007-23-08 at 07:33 -0400, Doug Bryant wrote: > This is most likely related to a copy node bug which has been fixed in > a .4 release. Ross fixed per an issue I opened. Although the .4 > release is labled as a pre-release, it is stable with the exception of > the memory bug. > > Upgrade and it will most likely fix the problem. > > See issue #4635 (now closed) > http://rubyforge.org/tracker/index.php?func=detail&aid=4635&group_id=494&atid=1971 >
Nope, that doesn't fix it. I have now produced a nice small test case, which is documented in this bug: http://rubyforge.org/tracker/index.php?func=detail&aid=13310&group_id=494&atid=1971 Since I now understand the bug, I can probably work round it. I can see that fixing this might be kinda tricky. I think that prior to freeing an xmlNode, libxml is going to have to walk the tree and remove any nodes that are referenced by ruby objects. __ Marc
signature.asc
Description: This is a digitally signed message part
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
