Issue 94132 - "select all" and copy cells may lead to crash
Summary: "select all" and copy cells may lead to crash
Status: CLOSED DUPLICATE of issue 59453
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOO300m7
Hardware: PC Windows, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-22 00:26 UTC by mhatheoo
Modified: 2008-10-15 07:22 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 mhatheoo 2008-09-22 00:26:55 UTC 
- have spreadsheet
- have a couple cells filled with any content in sheet A
- have a couple cells filled with any content in sheet B
-- Select ALL on sheet A and make a ctrl-C
-- select ALL on sheet B and make a ctrl-v

will last a couple of minutes and than crash with
"unexpected error from runtime"

Martin
Comment 1 oc 2008-09-22 10:37:24 UTC 
duplicate to #i59453#

*** This issue has been marked as a duplicate of 59453 ***
Comment 2 oc 2008-09-22 10:38:06 UTC 
closed because duplicate
Comment 3 mhatheoo 2008-09-22 13:20:19 UTC 
reopened

two reasons

-- it may or may not be a missunderstanding of the QA-team, but QA treat the
issue 59453 as the missing feature to "copy" any content to all cells of a sheet
that is - as stated -  an enhencement, but to a not needed feature.

In here it is a use of a "allowed" functions, that leads to a crash, so it is a
defect, and thereby different to issue 59453
But is does not make a diffence if you leave this issue open or set  56453 to
defect.


-- at second the error-message indicates, that there is no good error-handling
with memory-consuming jobs 

Just for your info: You have received this issue-report right after loosing the
work of quite long time, so I am not accepting setting a defect with data-loss 
be qualified as the need for an enhencement in far-out future.

Martin
Comment 4 oc 2008-10-15 07:21:40 UTC 
This one IS duplicate to #i59453#. Feel free to vote for i59453, but please
don't reopen this one.

*** This issue has been marked as a duplicate of 59453 ***
Comment 5 oc 2008-10-15 07:22:33 UTC 
closed as duplicate