Bug 131674 - Dragging sheet 2 before sheet 1 takes forever with 120k of comments
Summary: Dragging sheet 2 before sheet 1 takes forever with 120k of comments
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: perf
Depends on:
Blocks: Calc-Comments
  Show dependency treegraph
Reported: 2020-03-29 15:49 UTC by Telesto
Modified: 2022-08-12 03:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-03-29 15:49:02 UTC
Dragging sheet 2 before sheet 1 takes forever with 120k of comments

Steps to Reproduce:
1. Open attachment 156113 [details]
2. Insert a new sheet
2. Drag Sheet 2 before sheet 1 & wait, wait wait

Actual Results:

Expected Results:
More efficient way

Reproducible: Always

User Profile Reset: No

Additional Info:
Version: (x64)
Build ID: 7ae9c9572ccac55c0926b8a9779bb63c4236291c
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Telesto 2020-04-05 20:37:03 UTC
Deleting a column/row is also slow
Comment 2 b. 2020-05-11 00:41:51 UTC
for the BUG Hunting Session 7.0.0.a1+: 

1st move, empty sheet2 before sheet1 - less than a second 

2nd movement, sheet 1 with comments back again before sheet 2 - kiss your computer good night, maybe it will talk to you again tomorrow ... 

i've an unsure feeling that there are some improvements, it's possible to get focus on other maps / files - after reasonable wait - in win and work in them, but the main problem isn't solved ... 

linux (debian) worse than windows, system freeze, but both unusable :-(

ver. already affected /win - crash), probably inherited from OOo

'new', not a dup but 'related' to plenty other comment slowdown bugs
Comment 3 QA Administrators 2022-08-12 03:50:06 UTC
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team