Memory usage is high when you create several XmlSerializer objects in ASP.NET


In Microsoft ASP.NET, the memory usage increases unexpectedly when you create several XmlSerializer objects.


This problem occurs because an assembly that contains Microsoft intermediate language (MSIL) is created and loaded into memory when you create an XmlSerializer object. You cannot unload the assembly without unloading the application domain that it resides in. Therefore, when you create several XmlSerializer objects, you may notice unexpectedly high memory usage.

For example, if you use the following constructor to create several XmlSerializer objects, a new dynamic assembly is created every time:
public void XmlSerializer( Type t, Type[] extraTypes)


To work around this problem of re-creating dynamic assemblies, use one of the following methods:
  • Create one instance of the XmlSerializer class, and put that instance in the cache by using the caching APIs. For example, for a .dll file that is named HighSchool, the following code caches one instance of the XmlSerializer class:
    XmlSerializer mySerializer = new XmlSerializer(typeof(HighSchool.MyClass), attrOverrides, extraTypes, root, "");
    Cache["HighSchoolSerializer"] = mySerializer
    Use the instance of the XmlSerializer class that you put in the cache instead of creating a new XmlSerializer object every time.
  • Use the following XmlSerializer class constructors. These class constructors cache the assemblies:
    In the .NET Framework version 1.0
     public XmlSerializer(Type);

    In the .NET Framework version 1.1
    public XmlSerializer(Type type);
    public XmlSerializer(Type type, string defaultNamespace); 
  • Declare the XmlSerializer object to be a static member of a class.


For additional information about the XmlSerializer class and about the XmlSerializer class constructors, visit the following Microsoft Developer Network (MSDN) Web sites:

Article ID: 886385 - Last Review: Feb 24, 2012 - Revision: 1

Microsoft .NET Framework 4, Microsoft .NET Framework 2.0, Microsoft .NET Framework 1.1, Microsoft .NET Framework 1.0