Bug 134513 - EDITING: Librecalc slows down incredibly (or crashes) if you Ctrl-Down in a column with rows having more than a handful of formulas and the lowest modified row is a formula.
Summary: EDITING: Librecalc slows down incredibly (or crashes) if you Ctrl-Down in a c...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Performance
  Show dependency treegraph
 
Reported: 2020-07-04 23:25 UTC by Am Jam
Modified: 2021-09-15 03:38 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
copied from bug description (9.23 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-07-20 20:03 UTC, Terrence Enger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Am Jam 2020-07-04 23:25:27 UTC
Description:
Something strange happens if I hit Ctrl+Down. Suppose the following condition are met:
1. A column has "more than a handful of formulas" (in my bug tests I need at least 19, but I don't think this is some magic number -- it could be 19 on my 
machine given my hardware and 25 for you)
2. The last modified row (say, around row 200), is a formula
3. I'm on the last modified row

If these condition are met and I hit Ctrl+Down to warp to the lowest possible row (row 1048576 on my machine), then libreoffice gets VERY slow and sometimes crashes if the number of formulas is higher than 19 (in my case). 

My hardware is as follows:
Processor: Intel i7-10875H 5.1Ghz
RAM: 32G Dual Channel DDR4 at 3200Mhz
Gfx: NVidia RTX 2070 w/ 2304 CUDA Cores

Steps to Reproduce:
Suppose the following condition are met:
1. A column has "more than a handful of formulas" (in my bug tests I need at least 19, but I don't think this is some magic number -- it could be 19 on my 
machine given my hardware and 25 for you)
2. The last modified row (say, around row 200), is a formula
3. I'm on the last modified row

If these condition are met and I hit Ctrl+Down to warp to the lowest possible row (row 1048576 on my machine), then libreoffice gets VERY slow and sometimes crashes if the number of formulas is higher than 19 (in my case). 

I'm not sure how to share a spreadsheet in this bug tracker, so I've pasted my spreadsheet below so you can cut/paste.

ROW        COLUMN A
 1         476
 2         1561
 3         -152
 4         =SUM(A2:A3)
 5
 6         =A4
 7         =A63
 8         =A6-A7
 9
10         340
11
12         225
13         -140
14         1
15         11
16         32
17         0
18         -16
19         1
20         =3+51
21
22         169
23         222
24         =-209+303-541
25         0
26         0
27         0
28         =-430+387
29         "=SUM(A10,A12:A20,A22:A28)"
30
31         -200
32         =-148+220
33         0
34         =25-90
35         0
36         -185
37         -3
38         =SUM(A31:A37)
39
40         0
41         -2
42         263
43         0
44         -248
45         0
46         0
47         -183
48         0
49         =-10
50         =SUM(A40:A49)
51
52         0
53
54         619
55         942
56         =SUM(A54:A55)
57
58         1561
59         -152
60         =SUM(A58:A59)
61
62         =A60
63         933
64         =A62-A63
65
66         "=IF(ROUND(A64,2)=ROUND(A1,2),""-"",""Error"")"
67         "=IF(ROUND(A64,2)=ROUND(A8,2),""-"",""Error"")"


Actual Results:
Librecalc gets VERY slow if I try to use my arrow keys to move around cells near the bottom of the spreadsheet, or if I try to Ctrl+Up back to the top. 

Expected Results:
Librecalc should remain quick and responsive.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
N/A.
Comment 1 Terrence Enger 2020-07-20 20:03:08 UTC
Created attachment 163335 [details]
copied from bug description

Note that A66 and A67 show #err:508.
Comment 2 Terrence Enger 2020-07-21 14:32:29 UTC
qa-admin has removed whiteboard QA:needsComment.  I presume that this
is an automated reaction to my comment 1.

My comment was largely an attempt to "show willing" when I could not
do anything more useful.  I am restoring keyword QA:needsComment in
the of attracting someone who can do something better.
Comment 3 sora34ce 2020-09-03 17:40:34 UTC
I haven't seen any problems when I did it on my recent version.

Version: 7.1.0.0.alpha0+
Build ID: 52820b52b3bca45e2db527d1cc5f4488b2e0b9d0
CPU threads: 8; OS: Mac OS X 10.15.6; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 4 Xisco Faulí 2021-02-15 18:19:53 UTC
Hello Am Jam,
Thank you for reporting the bug.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 QA Administrators 2021-08-15 03:46:27 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-09-15 03:38:25 UTC
Dear Am Jam,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp