realbasic-nug
[Top] [All Lists]

Re: XmlDocument.ToString leak workarounds?

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: XmlDocument.ToString leak workarounds?
From: John Balestrieri <mrjohn at tinrocket dot com>
Date: Tue, 30 May 2006 11:18:26 -0400
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <f5c6a5400605300654t3acd438fr2e02ae7654a2e1cd at mail dot gmail dot com>
Another way to get a string out of an xml object is an SXLT stylesheet: XMLDocument.Transform

I don't have any off hand, but you should be able to search this list archive for a transform I posted that 'pretty prints' the XML

John


On May 30, 2006, at 9:54 AM, DeanG wrote:

"When XMLDocument.ToString is called and the XMLDocument is noticeable
large in size there is a major memory leak. The string object get set,
but the XMLDocument doesnt seem to release its memory when it goes out
of scope."

http://support.realsoftware.com/feedback/viewreport.php? reportid=iknjcmhx

What workaround exists for this?

Is it related to this?: Memory leak in XMLDocuments with XmlTextNodes

http://support.realsoftware.com/feedback/viewreport.php? reportid=rfgumccn

Thanks,

Dean
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

John Balestrieri
Tinrocket, LLC
www.tinrocket.com


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>