Few days ago I found out, that some of constructors of XmlSerializer can cause memory leak.
For example, public XmlSerializer(Type type, XmlRootAttribute root). Every time this constructor is called, it forces new assembly compilation and loading into AppDomain. So, after some time, there is a huge amount of equal assemblies in the AppDomain.
Now I have following questions to discuss: 1. Does Microsoft knows about this issue? 2. Why wasn't it fixed? 3. Does Microsoft knows any other memory leaks in .net BCL? 4. If does, where one can get the list of potential memory leaks scenarios in order to check one's application against this list?
Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.