Issue 74778 - inserting Writer OLE in Calc document results in crash
Summary: inserting Writer OLE in Calc document results in crash
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.2 RC1
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.2
Assignee: frank
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks: 73858
  Show dependency tree
 
Reported: 2007-02-22 14:43 UTC by mdxonefour
Modified: 2007-04-30 14:56 UTC (History)
4 users (show)

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

Attachments
The stack of the crash. (2.99 KB, text/plain)
2007-02-22 14:59 UTC, mikhail.voytenko 		no flags Details
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 mdxonefour 2007-02-22 14:43:47 UTC 
Open a new Calc sheet, type something, go throu the menu Inset->Object->OLE
Object and insert a new Writer OLE object. After this double click into the
Writer OLE object to start typing.
=> Result: Office crashes on double click
Comment 1 mikhail.voytenko 2007-02-22 14:59:03 UTC 
Created attachment 43274 [details]
The stack of the crash.
Comment 2 mikhail.voytenko 2007-02-22 15:00:23 UTC 
MAV->CD: The problem seems to be an asynchronous call to the layoutmanager
object that is already dead. Could you please take a look.
Comment 3 carsten.driesner 2007-02-22 17:56:25 UTC 
cd: Fixed. The layout timer must be stopped when the docking area acceptor
reference is set to null. Otherwise the timer code could access members which
are not valid anymore.
Comment 4 carsten.driesner 2007-02-23 06:56:51 UTC 
cd->oc: Please verify.
Comment 5 oc 2007-02-23 08:11:36 UTC 
Hi Frank, please take over
Comment 6 frank 2007-02-23 13:13:06 UTC 
no crash on cws olecrash01 anymore
Comment 7 frank 2007-04-27 14:02:39 UTC 
FST: Found fixed on master OOFm15 using Linux, Solaris and Windows build
Comment 8 frank 2007-04-30 14:56:21 UTC 
FST: Found fixed on master SRC680_m211 using Linux, Solaris and Windows build