To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113601
                 Issue #|113601
                 Summary|unoxml: When loading an ODF docment, UNO DOM::CDocumen
                        |t object, all UNO DOM::CNode and libxml DOM objects ar
                        |e leaked
               Component|framework
                 Version|OOO310m11
                Platform|All
                     URL|
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|mba
             Reported by|zhangjfibm





------- Additional comments from [email protected] Tue Aug  3 05:08:39 
+0000 2010 -------
Each time loading an ODF document, it created an UNO XML DOM tree and a
corresponding libxml DOM tree. The root node of UNO XML DOM tree is CDocument
node. In DOM::CDocument::~CDocument(), all uno dom nodes and libxml dom nodes
will be released. 

The problem is the created CDocument object is never released, because there are
cyclic reference between CDocument and all it's CNode objects.
CDocument.m_aNodeRefList keeps reference to all CNodes it creates while each
CNode.m_rDocument keep reference back to CDocument object.

The problem can be observed if you simply open/close any ODF documents.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to