Bug 89938 - Undo after pasting entire sheet causes LO to go runaway and freeze
Summary: Undo after pasting entire sheet causes LO to go runaway and freeze
Status: RESOLVED DUPLICATE of bug 85947
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.6.2 release
Hardware: Other All
: high critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, regression
Depends on:
Blocks:
 
Reported: 2015-03-10 19:09 UTC by tmacalp
Modified: 2015-12-15 11:03 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tmacalp 2015-03-10 19:09:20 UTC
Description:
Selecting an entire sheet, copying, pasting anywhere, and then trying to undo causes LO to go runaway and become unresponsive.  

Steps to reproduce:
1. Start new spreadsheet
2. ctrl-a to select entire sheet
3. ctrl-c to copy
4. ctrl-v to paste
5. ctrl-z to undo

Expected:
The paste operation should be undone and we should still have a working, responsive application.

Actual:
Congratulations, your LibreOffice is now runaway (using 100% cpu forever) and will be completely unresponsive.  You will now have to forcefully kill it.

Notes:
This is a really really horrible bug that is very easy to trigger.  I'm amazed that it hasn't already been reported.  I wouldn't be surprised to find this quickly marked as a duplicate.

I might be wrong, but since this essentially causes a crash in a common component and is VERY easy to reproduce, I'll set the severity to "Critical."

I'm not sure exactly which major version introduced the bug, but the earliest major version I have access to is 4.2.6, so I'll mark as such.  It affects every subsequent version, including 4.4.1.2.  Each version I've tested has been some variant of Linux, but I think this will affect multiple OSs.

Even though I don't know the exact major version, I've bibisected: e2ef0c10eb06304986b8503584b44f02561ce4b5 is the first bad commit
commit e2ef0c10eb06304986b8503584b44f02561ce4b5
Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
Date:   Sun May 11 07:43:35 2014 +0000

    source-hash-1b4aadebeb1898686313ff30ef47ddc4336a7444
    
    commit 1b4aadebeb1898686313ff30ef47ddc4336a7444
    Author:     Miklos Vajna <vmiklos@collabora.co.uk>
    AuthorDate: Wed Jan 29 22:33:58 2014 +0100
    Commit:     Miklos Vajna <vmiklos@collabora.co.uk>
    CommitDate: Wed Jan 29 22:39:10 2014 +0100
    
        writerfilter: these SPRM's are unused
    
        Change-Id: Ie2a25c592f7a75540b5bdc1c4958a1e4f86c2cc6

:100644 100644 465b41ea445be5b02f860c48c3f9f0218a7c857a 85f45f30feba11075310aa745a053a971ef1fec8 M    ccache.log
:100644 100644 8bd9bbb15f6d30a5cd2a8bba9e61df8fe802c833 470744529aea69fd6c7e11bfeb8a617a44cce560 M    commitmsg
:100644 100644 c70aaedacb567416d594b8e1bb16eed65d5990fd 73be70ccec187662ed9baac45a515c87da03aad6 M    make.log
:040000 040000 5479cfabe7b8a2c8a120caea61a83bc702475091 5566567c915a96b69c2ff95753bdf3730a195b70 M    opt


$ git bisect log
git bisect start 'latest' 'last42onmaster'
# bad: [4fcd68ce4979f85fda4568f4b419a4b41d07345f] source-hash-2c4621c87ed3a7b19de195c21494c9a381e72b2e
git bisect bad 4fcd68ce4979f85fda4568f4b419a4b41d07345f
# good: [0d4c20a601a3cfff27d6685d0e81463086bd9d74] source-hash-f1b1e73227471192682d303a58618ca8bd65a74d
git bisect good 0d4c20a601a3cfff27d6685d0e81463086bd9d74
# bad: [3c72d6d27e2a0c420f74941355400b0834c550bb] source-hash-c30677731c55688c764a669ecea1b1c4d17ae57d
git bisect bad 3c72d6d27e2a0c420f74941355400b0834c550bb
# bad: [1f32fb58159d7f43a4bcb838765261d5274cbf38] source-hash-4a169e4203c10ec8f76b9bcb33882c82b65c7bab
git bisect bad 1f32fb58159d7f43a4bcb838765261d5274cbf38
# good: [ee1097e0c6690c1e5a437f326b3b35b9b262420a] source-hash-cbc8a424f8e89202b9a2376f57175264bbd83381
git bisect good ee1097e0c6690c1e5a437f326b3b35b9b262420a
# good: [78299d579aaf6b0419b99bb858a7af62d1f4d3dc] source-hash-218c9cff53c36d3f6e744067d5812b883a60b459
git bisect good 78299d579aaf6b0419b99bb858a7af62d1f4d3dc
# skip: [c9046ea7e069426d10e071d0bcb01c64685844c6] source-hash-f5115e33e4c5e49e9b79ed32fccc193a99c3dc30
git bisect skip c9046ea7e069426d10e071d0bcb01c64685844c6
# bad: [2d8ee8e5bf8901874460df1b36b3faceae1cb931] source-hash-777e3930a1e85b9bc97c1852b09802fc389c5e2d
git bisect bad 2d8ee8e5bf8901874460df1b36b3faceae1cb931
# bad: [e2ef0c10eb06304986b8503584b44f02561ce4b5] source-hash-1b4aadebeb1898686313ff30ef47ddc4336a7444
git bisect bad e2ef0c10eb06304986b8503584b44f02561ce4b5
# first bad commit: [e2ef0c10eb06304986b8503584b44f02561ce4b5] source-hash-1b4aadebeb1898686313ff30ef47ddc4336a7444
Comment 1 tmacalp 2015-03-10 19:15:56 UTC
According to bug prioritization flowchart, I'm marking this up to at least "High" importance and have added bibisected/regression whiteboard/keywords.
Comment 2 raal 2015-03-10 19:38:02 UTC
Hello tmacalp,

Thank you for reporting the bug. This issue has previously been reported, so this bug will be resolved as a duplicate of the earlier report. You will automatically be added to the CC list of the other bug.

*** This bug has been marked as a duplicate of bug 85947 ***
Comment 3 Robinson Tryon (qubit) 2015-12-15 11:03:11 UTC
Migrating Whiteboard tags to Keywords: (bibisected)
[NinjaEdit]