Bug 93180 - Calc crash on copy all cells from Table1 to Table2
Summary: Calc crash on copy all cells from Table1 to Table2
Status: RESOLVED DUPLICATE of bug 92797
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.5.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-06 07:39 UTC by ralf.krapf
Modified: 2015-08-06 10:55 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ralf.krapf 2015-08-06 07:39:50 UTC 
Ohoh, ugly Bug:

Steps to reproduce:

1. Create a new empty Calc document
2. Write "test" in Cell A1 from "Tabelle1"
3. Mark all cells by clicking in the upper left corner of cell A1
4. Create a new Table (in german called "Tabelle2") by pressing "+"
4. Copy all cells by clicking in the upper left corner of cell A1
5. Ctrl+C
6. Go to "Tabelle2"
7. Click in the upper left corner of cell A1
8. Ctrl+V
9. -> Calc hang up and Crash (LibreOffice 4.4 Fatal Error: bad allocation)

System:
LO 4.4.5.2 under W7 64bit and W10 64bit

Cheers
Ralf

btw: after 3 times soffice.bin *32 hangs up in the windows task manager, one of the instances has 1'531'152K memory, and two 895K of memory.
Comment 1 ralf.krapf 2015-08-06 07:43:27 UTC 
Sorry, here the corrected version:

1. Create a new empty Calc document
2. Write "test" in Cell A1 from "Tabelle1"
3. Mark all cells by clicking in the upper left corner of cell A1
4. Ctrl+C
5. Create a new Table (in german called "Tabelle2") by pressing "+"
6. Go to "Tabelle2"
7. Mark all cells by clicking in the upper left corner of cell A1
8. Ctrl+V
9. -> Calc hang up and Crash (LibreOffice 4.4 Fatal Error: bad allocation)
Comment 2 raal 2015-08-06 10:55:59 UTC 
Hello,

Thank you for submitting the bug. The bug has previously been reported, so this bug will be added as a duplicate of it. You will automatically be CCed to updates made to the other bug.

*** This bug has been marked as a duplicate of bug 92797 ***