Article ID: 316775 - View products that this article applies to.
This article was previously published under Q316775
This article has been archived. It is offered "as is" and will no longer be updated.
This article refers to the following Microsoft .NET Framework Class Library namespaces:
When you use the <msxsl:script> element repeatedly with System.Xml.Xslt framework, a memory leak may occur with a high volume Extensible Markup Language (XML) or Extensible Stylesheet Language (XSL) application.
The classes of the System.Xml namespace support the use of embedded scripting by using the script element in XSL Transformation (XSLT) applications. Therefore, the <msxsl:script> element allows you to choose the programming language (such as Microsoft Visual C# .NET or Microsoft Visual Basic .NET) to perform certain tasks.
Declared functions are contained within script blocks. When you use embedded script with an XSL file, an assembly that contains Microsoft Intermediate Language (MSIL) is created and loaded into memory. Because of a design limitation in this version of the Microsoft .NET Framework, you cannot unload that assembly from memory. This may lead to a memory leak if assemblies are created and loaded repeatedly or in a loop.
To resolve this problem, do not repeatedly load the XSLT with the script. Develop your application in such a way that you load the XSLT once and reuse it as many times as needed. This practice also improves performance.
For example, the following code leaks memory:
Change the code as follows to load XSLT only once and reuse it in a loop:
This code only loads the assembly once and does not leak memory.
Unload an individual assembly by unloading all the application domains that contain the assembly. To do this, call the AppDomain.Unload() method for each application domain that has the assembly loaded, or call the UnloadDomain() method on the unmanaged hosting API.
Steps to reproduce the behavior