Issue 105511 - integration.forms.XMLFormSettings crashes OOo
Summary: integration.forms.XMLFormSettings crashes OOo
Status: CLOSED DUPLICATE of issue 105520
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: DEV300m60
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 3.2
Assignee: Mathias_Bauer
QA Contact: issues@dba
URL:
Keywords: crash, regression
Depends on:
Blocks: 99999
  Show dependency tree
 
Reported: 2009-10-01 11:09 UTC by Frank Schönheit
Modified: 2009-10-19 10:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2009-10-01 11:09:00 UTC 
running the integration.forms.XMLFormSettings test from forms/qa (dmake
run_XMLFormSettings) crashes OOo.
Comment 1 Frank Schönheit 2009-10-01 11:12:33 UTC 
That's a regression between DEV300 m59 and m60
Comment 2 Frank Schönheit 2009-10-01 11:20:37 UTC 
fs->mba: The stack is as follows:
  SfxViewShell::GetController()
  SfxClipboardChangeListener::disposing
  cppu::OInterfaceContainerHelper::disposeAndClearbytes
  cppu::OMultiTypeInterfaceContainerHelper::disposeAndClear
  sfxmi.dll!SfxBaseController::dispose
The SfxClipboardListener has a member pViewShell, which points to an
already-dead object, instead of being NULL.
Comment 3 mikhail.voytenko 2009-10-05 10:34:29 UTC 
That looks like a duplicate to issue 105343, that is fixed in fwk122.
SfxClipboardChangeListener is not notified that the SfxViewShell object already
deleted.

*** This issue has been marked as a duplicate of 105343 ***
Comment 4 mikhail.voytenko 2009-10-05 12:16:36 UTC 
Just for information, the test reloads the document explicitly, this is how it
gets to the scenario from issue 105343.
Comment 5 mikhail.voytenko 2009-10-09 13:24:58 UTC 
reopening
Comment 6 mikhail.voytenko 2009-10-09 13:26:14 UTC 
In reality it is a duplicate of the issue 105520. The issue 105543 looks to be a
different problem.

*** This issue has been marked as a duplicate of 105520 ***
Comment 7 Mechtilde 2009-10-19 10:16:50 UTC 
duplicate -> closed