To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=68977
User cd changed the following:
What |Old value |New value
================================================================================
Status|STARTED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Sep 14 01:00:08 -0700
2006 -------
cd->cmc: A ModuleImageManager is normally provided by a
ModuleUIConfigurationManager which is a one instance service. Therefore the
ModuleImageManager will be disposed at the end of the Office life-time. That's
why I think this is not a real "memory leak". As it can confuse developers which
uses a memleak tool, I think we should fix it. From my point of view your patch
should be added to the "dispose" method and not to the dtor. It's not always
clear when a component (supports XComponent) will be destroyed. It's possible
that some resources are already de-initialized (e.g. VCL) and calling delete on
VCL objects can lead to crashes. Therefore all resources should be
released/destroyed in dispose.
---------------------------------------------------------------------
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]
