[4suite] Memory leaks not fixed in 4suite0.9rc1

[Uche Ogbuji]

Alexandre Fayolle wrote:

> Some memory leaks I had mentionned over the past few weeks are
> still in RC1:
> 
> * no call to ReleaseNode in StripHtml and StripXml in xml.dom.ext
> (reported on august 12)

This is not a circular reference.  The problem you were seeing was that
there were _other_ circuler references that were tying nodes back to the
owner document.  Now that we've cleaned those up, removeNode is clean. 
The node still has a reference to the ownerDocument, but there is no
direct or indirect refeerence back from the document.  Cyclops confirms
this.  If you're seeing otherwise, please post a brief scenario of
what's going on.

> * reference leaks in  Sax2.FromXmlStream (patch submitted on august 28)

I thought we checked this and found no leak here either after the core
fixes.  Let me confirm.

In general, could you run test_suite/test_memory.py from DOM?  You'll
need to pipe in an XML file.  Let us know whether you find cycles. 
Cyclops.py is available from our FTP at mirrors/etc.  It will be bundled
with the final release.

Can you post sample snippets of code that illustrate leaks?  If you're
familiar with Cyclops (easy enough to use: just see test_memory.py for
one approach) reports therefrom would help.

Thanks.

-- 
Uche Ogbuji                               Principal Consultant
uche.ogbuji at fourthought.com               +1 303 583 9900 x 101
Fourthought, Inc.                         http://Fourthought.com 
4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA
Software-engineering, knowledge-management, XML, CORBA, Linux, Python