Issue 127691 - Copy & Paste Into Sheet With All Cells Selected Crashes OO
Summary: Copy & Paste Into Sheet With All Cells Selected Crashes OO
Status: CLOSED DUPLICATE of issue 59453
Alias: None
Product: Calc
Classification: Application
Component: editing (show other issues)
Version: 4.1.5
Hardware: PC Windows 10
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-06 21:48 UTC by zgbrown07
Modified: 2018-02-09 21:20 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description zgbrown07 2018-02-06 21:48:13 UTC
I have found similar bugs reported, but they deal with the program running out of memory and either hanging or crashing. This bug results in a crash immediately after executing a paste without hangups or memory exhaustion.

In my case, I am copying 150 rows and three columns to an existing sheet. The data being copied includes functions and text color, and a few have color conditions (red if negative value). I clear the existing sheet by clicking on A1 then using ctrl+a and delete, and select delete all. Once the sheet is cleared, it remains highlighted with A1 as focus. When I paste into this sheet with ctrl+v, the program crashes without hesitation. I have tested this event four times, each with the same result. I further tested this by creating a new sheet, and only selecting A1 then pasting. The program pastes as normal. When I select all after clicking A1 and paste, the program crashes.

I am reasonably sure 18 GB of memory is sufficient to handle such executions, and the fact that the program doesn't “wait and think” about what is happening leads me to believe this is a unique bug. I would also consider it somewhat important because selecting all to clear a sheet before pasting is a common step.
Comment 1 Marcus 2018-02-09 21:19:40 UTC
already reported, therefore duplicate

*** This issue has been marked as a duplicate of issue 59453 ***