If broken it is, fix it you should


May, 2010

  • If broken it is, fix it you should

    .NET Memory Leak: XslCompiledTransform and “leaked” dynamic assemblies

    I have written before about high memory usage caused by improper usage of XmlSerializer objects both in a case study and in a debugging lab .  The problem there was that every time you create a new XmlSerializer object with a non-default constructor, you generate a new dynamic assembly that contains the definition and methods for the serializer.  Since assemblies can’t be unloaded from a process unless the application domain they are loaded in is unloaded memory will keep increasing if...
Page 1 of 1 (1 items)