Description: Slow scrolling responsiveness after saving a file with lots of comments Steps to Reproduce: 1. Open the attached file 2. Scroll around (OK) 3. Press CTRL+S & scroll up/down or switch to a different task and back to Libo Actual Results: Really slow Expected Results: Faster Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.0.0.alpha0+ (x86) Build ID: 93477d1a963e38e3319013e43835a8ffef200972 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-06-02_10:16:52 Locale: it-IT (nl_NL); UI-Language: en-US Calc: threaded also with 5.2.2.2 Crash with 4.4.7.2
Created attachment 151850 [details] Example file
Repro Version: 6.4.0.0.alpha0+ (x64) Build ID: 7272b9f752cb74757d6ed504202eefccc589f804 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-06-01_03:59:41 Locale: es-ES (es_ES); UI-Language: en-US Calc: threaded
Not sure if it's worth it, but bibisecting the point where the crashing stops/ slowness starts might give some insight
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 MassPing-UntouchedBug
Slow scrolling in the example file now even without first saving.
I also get a huge slowdown and lag with the example file in OOo 3.3. Telesto, any reason why this shouldn't be a duplicate of bug 61558?
(In reply to Stéphane Guillou (stragu) from comment #6) > I also get a huge slowdown and lag with the example file in OOo 3.3. > Telesto, any reason why this shouldn't be a duplicate of bug 61558? It's a duplicate of bug 125619. Is bug 125619 being a duplicate of bug 61558? I don't really know. Based on my vague recollection, not testing.... There is a difference between a calc document with lots of comments, but hidden. And a document with lots of comments with those comments all visible (expanded) Both slow but maybe a different cause. There is difference between scrolling before and after save and a good state. at bug 125619, but might be simply the old problem uncovered in different way? Or the perf was omni-present in 3.3.0, problem got resolved for this case by incident or on purpose, but got re-introduced for different reason? The slowness of this bug and bug 125619 could also be explained by bug 131675 (still present?).. different perspective on the same problem or a third separate issue exacerbating the problems Sidenote I tend to assume multiple bugs being chased with the end-user effect colliding (slow scrolling), except proven otherwise. I personally dislike marking things duplicates easily. It might hide that multiple issues exists. And a bug report becoming a real mess, if multiple reports start te comment on their own bug case, and the cause being different. And rechecking duplicates - if those being true duplicates - after a fix isn't done on a regular bases either. Ideally (often) you don't need to - it's a waste of time - duplicates being true duplicate *** This bug has been marked as a duplicate of bug 125619 ***