Hello,

I have just found a serious memory leak in dotcmis. The function "DeserializeElement" in converter.cs is leaking. I have tried to load a type definition multiple times without reusing the session object.(I have always created a new one.) The type definition contains a large set of "choices". Doing so will flood the memory. The memory leak is located in the XmlSerializer constructor. Please take a look at this article describing the issue: http://www-jo.se/f.pfleger/memoryleak Microsofts suggestion is to reuse the XmlSerializer class or to use another constructor.

Thank You
Björn


Reply via email to