To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113743
------- Additional comments from i...@openoffice.org Wed Aug 18 10:53:27 +0000 2010 ------- I now have checked the not so obvious scenarios for this leak. There are still problems. Load the attached document DataPointMemoryLeak.ods and run the macro. While running the macro multiple times look at the soffice.bin process. It is consuming more and more memory. The macro does the following: A second series is added to a chart. One data point of the second series is given a color (this creates the data point and the cyclic reference). The series is removed from the chart again by choosing a different cell range. This is done multiple times. Conclusion: The XComponent interface is not the correct pattern to fix this memory leak because the series objects do not always have a defined owner. The correct approach here is to use weak references instead of hard references. A weak reference does not keep the object alive it points to. This pattern avoids the cyclic reference completely in advance and has no administrative overhead - very elegant. --------------------------------------------------------------------- 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: issues-unsubscr...@graphics.openoffice.org For additional commands, e-mail: issues-h...@graphics.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
