realbasic-nug
[Top] [All Lists]

XmlDocument.ToString leak workarounds?

To: realbasic-nug at lists dot realsoftware dot com
Subject: XmlDocument.ToString leak workarounds?
From: DeanG <goodmansond at gmail dot com>
Date: Tue, 30 May 2006 08:54:45 -0500
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=A7TlqngyLwruenr0ft/mvwr84+voaGvnACVYhdPqJR7U6B36VsGMaESwgVvsN9tVH4THpVoUSvj7IM5SJHRnhN3rA5xCnWrUZglMQ+EYasvvknTbuF3JZYTP5tn9tPx3asZ6BXK5PQbxHb85APNirRdGeDjkAjVNEByxMU96QcA=
"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>


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