Issue 16491 - Draw CRASH when copying
Summary: Draw CRASH when copying
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Draw
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC All
: P2 Trivial (vote)
Target Milestone: OOo 1.1
Assignee: wolframgarten
QA Contact: issues@graphics
URL: http://kosh.datateamsys.com/~danny/OO...
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-07-05 22:43 UTC by dannyb
Modified: 2003-09-08 16:52 UTC (History)
1 user (show)

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

Attachments
Stack dumps from gdb and valgrind (14.43 KB, text/plain)
2003-07-06 03:02 UTC, dankegel 		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 dannyb 2003-07-05 22:43:45 UTC 
Download this drawing.

http://kosh.datateamsys.com/~danny/OOo/BugAttachment/Hue%20Rainbow.sxd

Steps to reproduce crash.

1. Open the document "Hue Rainbow.sxd"

2. File -> New -> Text Document

3. Switch back to the Hue Rainbow document by clicking in it.

4. Select the bottom rainbow.  (The one which is a Bitmap.  The top one is an
OOo drawing of many small rectangles produced by a StarBasic program.)  Select
the BOTTOM rainbow, not the top one.

5. Ctrl-C  (intention is to Copy)

6. Switch to text document created in step 2 by clicking in it.

7. Ctrl-V  (intention is to Paste)

8. Switch back to Hue Rainbow document.

9. Select the draw group of arrows and text that is beneath the bottom rainbow.

10. Ctrl-C  (intention is top Copy)

11. Switch to the text document created in step 2 by clicking in it.


Pointer turns into an hourglass.  OOo never responds after this point.

I am on Windows XP Pro.  512 MB.  P4 1800 MHz.  OOo 1.1 Beta 2.  I can reproduce
100 %.

I can NOT reproduce this in OOo 1.0.1 as shipped with SuSE Linux 8.1.
Comment 1 dankegel 2003-07-06 03:02:12 UTC 
Reproduced on Linux with gdb.  Looks like it's doing a four byte
read or write at address zero.  Tsk.  I'll attach the stack traceback
next.
Comment 2 dankegel 2003-07-06 03:02:50 UTC 
Created attachment 7433 [details]
Stack dumps from gdb and valgrind
Comment 3 wolframgarten 2003-07-07 07:51:47 UTC 
This is reproduceable in version 1.1beta2 but not in a current
internal one. Nevertheless I reassign this to Christian. Maybe the
stack contains some useful information...
Comment 4 clippka 2003-07-07 12:13:06 UTC 
This was one of our ole issues and is already fixed
Comment 5 wolframgarten 2003-07-07 12:20:47 UTC 
Set this to worksforme. The fix will be available in the 2.0. Thanks
for your help.
Comment 6 wolframgarten 2003-07-07 12:21:04 UTC 
Closed.