A quick Google on 'MSXML memory leak' comes up with this article:
http://support.microsoft.com/support/kb/articles/Q293/0/80.ASP
'After you add an XMLDOMDocument or XMLDOMNode object to an Extensible
Stylesheet Language (XSL) template that is cached in an Active Server Pages
(ASP) Application variable, and you set an XSLProcessor object in a second
ASP page to use the cached Application level template as a parameter, the
XSLProcessor object's transform method consumes a large amount of memory.
You only see memory usage grow if the XSL template is cached at the ASP
Application level. You do not see the memory leak if you create a new XSL
template every time that the XSLProcessor object is used.'
Apparently it's fixed in MSXML3 service pack 1.
Tom
P.S. Just seen Jeremy's post. Woo hoo! Horse's mouth and all that.
> I recall reading in the ms xml newsgroup on MS's news server
> that MS XML was leaking. Perhaps the leak issue is gone. But,
> heck, this is MS we are talking about... ;)
>
> James Ang
> Webmaster, TekBay.com
> [EMAIL PROTECTED]
-----------------------+
cf-xml mailing list
[EMAIL PROTECTED]
http://torchbox.com/xml
