Issue 58600 - OpenOffice sometime crashes after close Application
Summary: OpenOffice sometime crashes after close Application
Status: CLOSED DUPLICATE of issue 56370
Alias: None
Product: Impress
Classification: Application
Component: editing (show other issues)
Version: OOo 2.0
Hardware: All Windows 2000
: P2 Trivial (vote)
Target Milestone: ---
Assignee: wolframgarten
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-29 06:39 UTC by jlcheng
Modified: 2005-12-06 08:41 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 jlcheng 2005-11-29 06:39:35 UTC 
Steps to replicate:

1) Created a new impress.

2) To slide master by menu View->Master->Slide Master.

3) Draw one rectangle on default Slide Master.
 Input some text in the rectangle.
 Use Ctrl+C Copy the rectangle.
 Move the rectangle anyway.
 Use Ctrl+V Paste the rectangle.
 "Close Master View" by Master View Dialog.
 Close impress.
 Close OpenOffice Application.
4) OK. You can find CPU is up nearly 100%. If you use release version, you can
not find some bad thing, only SOMETIMES OpenOffice crashes(and nearly does not
have, only SOMETIMES after repeat step 1 to step 3 many times).
 But if you run DEBUG version, you can find sometime get Exceptions after Closed
OpenOffice Application. And only SOMETIMES OpenOffice crashes.


I think this maybe Big Paste problem of Impress, and not only Master have this
Paste problem. I think should find the real reason.
Comment 1 wolframgarten 2005-11-29 07:49:11 UTC 
Changed poririty.
Comment 2 jlcheng 2005-12-01 05:13:29 UTC 
Sorry,
new 2.0.1 is ok. And I find maybe duplicate of 56370. And I set wrong Version to
OOo 2.0.1, in fact reproducible on Version OOo 2.0.0.
Comment 3 wolframgarten 2005-12-01 08:30:28 UTC 
Version changed.
Comment 4 atdsm 2005-12-05 17:42:19 UTC 
Agreed, this seems to be a duplicate of 56370. Issue 56370 is marked as fixed;
jlcheng says problem is fixed in 2.0.1.

Marking as duplicate.

Steve

*** This issue has been marked as a duplicate of 56370 ***
Comment 5 wolframgarten 2005-12-06 08:41:30 UTC 
Thanks, closing.