You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2013/05/16 11:07:17 UTC

[jira] [Updated] (CMIS-657) Memory leak in DotCMIS

     [ https://issues.apache.org/jira/browse/CMIS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Müller updated CMIS-657:
--------------------------------

    Fix Version/s: DotCMIS 0.6
    
> Memory leak in DotCMIS
> ----------------------
>
>                 Key: CMIS-657
>                 URL: https://issues.apache.org/jira/browse/CMIS-657
>             Project: Chemistry
>          Issue Type: Bug
>          Components: dotcmis
>    Affects Versions: DotCMIS 0.5
>            Reporter: Björn
>            Assignee: Florian Müller
>             Fix For: DotCMIS 0.6
>
>
> 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. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira