To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=113992
                 Issue #|113992
                 Summary|Backup ChartModel object leaks when opening chart dial
                        |og
               Component|Chart
                 Version|OOO310m11
                Platform|All
                     URL|
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|PATCH
                Priority|P2
            Subcomponent|ui
             Assigned to|iha
             Reported by|zhangjfibm





------- Additional comments from zhangjf...@openoffice.org Thu Aug 19 13:55:50 
+0000 2010 -------
This is another obvious leak from chart module we recently identified.

Below is the steps to recreate the memory leak,
  1. new a sc document
  2. insert a chart, it then shows the chart dialog, then click finish. After
that click on any cells to switch from inplace frame mode back to normal edit 
view
  3. close the doc


The callstack which creates the leaked object is,

        chartmodelmi!chart::ChartModel::createClone+0000002C
(z:\calc\chart2\source\model\main\chartmodel.cxx, 880)
        chartcontrollermi!chart::DialogModel::createBackup+000000D0
(z:\calc\chart2\source\controller\dialogs\dialogmodel.cxx, 798)
        chartcontrollermi!chart::DialogModel::DialogModel+00000143
(z:\calc\chart2\source\controller\dialogs\dialogmodel.cxx, 387)
        chartcontrollermi!chart::CreationWizard::CreationWizard+0000020C
(z:\calc\chart2\source\controller\dialogs\dlg_creationwizard.cxx, 99)
        
chartcontrollermi!chart::CreationWizardUnoDlg::createDialogOnDemand+00000256
(z:\calc\chart2\source\controller\dialogs\dlg_creationwizard_uno.cxx, 240)
        chartcontrollermi!chart::CreationWizardUnoDlg::getPropertyValue+0000032B
(z:\calc\chart2\source\controller\dialogs\dlg_creationwizard_uno.cxx, 393)
        scmi!FuInsertChart::FuInsertChart+00001477
(z:\calc\sc\source\ui\drawfunc\fuins2.cxx, 752)
        scmi!ScTabViewShell::ExecDrawIns+000002DD
(z:\calc\sc\source\ui\view\tabvwshb.cxx, 373)
        scmi!SfxStubScTabViewShellExecDrawIns+0000000F
(z:\calc\sc\wntmsci10.pro\inc\scslots.hxx, 1258)
        sfxmi!SfxDispatcher::Call_Impl+000004AF
(z:\lib\sfx2\source\control\dispatch.cxx, 306)
        sfxmi!SfxDispatcher::PostMsgHandler+000000DE
(z:\lib\sfx2\source\control\dispatch.cxx, 1619)
        sfxmi!SfxDispatcher::LinkStubPostMsgHandler+0000000F
(z:\lib\sfx2\source\control\dispatch.cxx, 1579)
        tlmi!Link::Call+00000022 (z:\lib\tools\inc\tools\link.hxx, 142)
        sfxmi!SfxHintPoster::Event+0000003A 
(z:\lib\sfx2\source\notify\hintpost.cxx, 93)
        sfxmi!SfxHintPoster::LinkStubDoEvent_Impl+00000012
(z:\lib\sfx2\source\notify\hintpost.cxx, 87)
        tlmi!Link::Call+00000022 (z:\lib\tools\inc\tools\link.hxx, 142)
        vclmi!ImplHandleUserEvent+000000AC 
(z:\lib\vcl\source\window\winproc.cxx, 2024)
        vclmi!ImplWindowFrameProc+00000635 
(z:\lib\vcl\source\window\winproc.cxx, 2613)
        vclmi!ImplHandleUserEvent+00000042 
(z:\lib\vcl\win\source\window\salframe.cxx,
4804)
        vclmi!SalFrameWndProc+0000081E 
(z:\lib\vcl\win\source\window\salframe.cxx, 6463)
        vclmi!SalFrameWndProcW+00000054 
(z:\lib\vcl\win\source\window\salframe.cxx, 6686)
        USER32!InternalCallWinProc+00000028
        USER32!UserCallWinProcCheckWow+00000150
        USER32!DispatchMessageWorker+00000306
        USER32!DispatchMessageW+0000000F
        vclmi!ImplDispatchMessage+00000016 
(z:\lib\vcl\win\source\app\saldata.cxx, 189)
        vclmi!ImplSalDispatchMessage+00000037 
(z:\lib\vcl\win\source\app\salinst.cxx, 71


The root cause of this leak is,

DialogModel.xBackupChartDocument is created in DialogModel constructor API with
api DialogModel.createBackup(). While in it's Dtor, xBackupChartDocument is not
completely released because of cyclic reference inside ChartModel object.
Normally before it is released, xBackupChartDocument.dispose() should be called
first to break the cyclic reference, but this call is missing.

---------------------------------------------------------------------
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

Reply via email to