KB 316775 reproes in .net 1.1 - XSLT with script has memory leak

[John Moore]

I have a set of code that is called on every page load that loads an xslt
file. The xslt file has an embedded <script> tag. Loading the page mutliple
times causes aspnet_wp.exe to use all available memory and then reset. As
this happens several times over the course of an 8 hour stress run, I'm
looking for a solution.

The xslt file has the following:
<xsl:if test="$strPageC aller=''">
<SCRIPT LANGUAGE="JavaS cript">BPB()</SCRIPT>
</xsl:if>
<xsl:if test="$strPageC aller!=''">
<SCRIPT LANGUAGE="JavaS cript">if (history.length > ((bNS)?1:0))
document.write( "<A class='p1s23'
href='Javascrip t:history.go({$ strPageCaller}) ;'><B>Return to
Previous</B></A>");</SCRIPT>
</xsl:if>

The calling code is this:
XmlDocument l_objXMLDoc = new XmlDocument();
System.IO.Strin gWriter l_objWriter = null;
XslTransform xslt = null;
l_objXMLDoc.Loa dXml(m_strXML);

// Create an XPathNavigator to use for the transform.
XPathNavigator nav = l_objXMLDoc.Cre ateNavigator();

// Transform the file.
l_objWriter = new System.IO.Strin gWriter();
xslt = new XslTransform();
xslt.Load(Serve r.MapPath(
ConfigurationSe ttings.AppSetti ngs["XSLT_PATH"] // get path for xslt file
storage
+
"/xsltfile.xslt") // append physical filename to path
);

xslt.Transform( nav, l_objargList, l_objWriter, null );
l_strOutput = l_objWriter.ToS tring();

The system configuration is win2k advanced server with latest service pack
and dot net 1.1.

Any ideas?

John

[Ken Cox [Microsoft MVP]]

Hi John,

I take it the workaround in the article wasn't any use to you.

Make sure you report it as a 1.1 bug as well?

Here's where: http://lab.msdn.microsoft.com/produc...k/default.aspx
"John Moore" <John Mo***@discussio ns.microsoft.co m> wrote in message
news:46******** *************** ***********@mic rosoft.com...

I have a set of code that is called on every page load that loads an xslt
file. The xslt file has an embedded <script> tag. Loading the page
mutliple
times causes aspnet_wp.exe to use all available memory and then reset. As
this happens several times over the course of an 8 hour stress run, I'm
looking for a solution.

The xslt file has the following:
<xsl:if test="$strPageC aller=''">
<SCRIPT LANGUAGE="JavaS cript">BPB()</SCRIPT>
</xsl:if>
<xsl:if test="$strPageC aller!=''">
<SCRIPT LANGUAGE="JavaS cript">if (history.length > ((bNS)?1:0))
document.write( "<A class='p1s23'
href='Javascrip t:history.go({$ strPageCaller}) ;'><B>Return to
Previous</B></A>");</SCRIPT>
</xsl:if>

The calling code is this:
XmlDocument l_objXMLDoc = new XmlDocument();
System.IO.Strin gWriter l_objWriter = null;
XslTransform xslt = null;
l_objXMLDoc.Loa dXml(m_strXML);

// Create an XPathNavigator to use for the transform.
XPathNavigator nav = l_objXMLDoc.Cre ateNavigator();

// Transform the file.
l_objWriter = new System.IO.Strin gWriter();
xslt = new XslTransform();
xslt.Load(Serve r.MapPath(
ConfigurationSe ttings.AppSetti ngs["XSLT_PATH"] // get path for xslt file
storage
+
"/xsltfile.xslt") // append physical filename to path
);

xslt.Transform( nav, l_objargList, l_objWriter, null );
l_strOutput = l_objWriter.ToS tring();

The system configuration is win2k advanced server with latest service pack
and dot net 1.1.

Any ideas?

John