Bug 42031 - copying entire columns locks up Calc
Summary: copying entire columns locks up Calc
Status: RESOLVED DUPLICATE of bug 40958
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-19 23:56 UTC by Kevin Hunter
Modified: 2011-12-16 16:52 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Example document to show lock up copying columns (24.12 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-10-19 23:56 UTC, Kevin Hunter 		Details
View All 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 Kevin Hunter 2011-10-19 23:56:41 UTC 
Created attachment 52569 [details]
Example document to show lock up copying columns

Calc locks up attempting to copy entire columns.  Steps to reproduce with attached spreadsheet

-----
1. Select Sheet1

2. Select columns A, B, and C by clicking and dragging from the header of Column A through the header of Column C.

3. Hit Ctrl+C to copy to clipboard.

4. Select entire column of G by clicking on the G column header.

5. Hit Ctrl+V (paste from clipboard) and watch LO lock up.
-----

This is current behavior with an update master as of 20 Oct 2011

$ git log -1 --format=oneline 5ad4d151dac1eb887d92200330e31af269d8d1fd migrate to StringRangeEnumerator in pdfexport
Comment 1 tester8 2011-10-20 12:44:21 UTC 
NOT reproduced with

LO 3.4.3 OOO340m1 (Build:302)
Ubuntu 10.04.3 x86
Linux 2.6.32-34-generic Russian UI

x64 specific???
Comment 2 Kevin Hunter 2011-10-20 16:50:03 UTC 
@tester8

Can you test with a development build?  It may be x64 specific, but my immediate hunch is that this is broken recently in the code base.

If someone else can reproduce my lock-up results on Master, then we have two ends for a git bisection process.
Comment 3 Markus Mohrhard 2011-12-16 16:52:46 UTC 
I'm quite sure that it has the same solution as bug 40958. We changed copy behavior between 3.4 and 3.5 and that creates this problem.

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