Bug Hunting Session
Bug 125641 - Slow scrolling responsiveness after saving a file with lots of comments
Summary: Slow scrolling responsiveness after saving a file with lots of comments
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, perf
Depends on:
Blocks: Scrolling-PageUpDown
  Show dependency treegraph
 
Reported: 2019-06-02 13:43 UTC by Telesto
Modified: 2019-06-03 21:47 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example file (40.93 KB, application/vnd.oasis.opendocument.text)
2019-06-02 13:44 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2019-06-02 13:43:34 UTC
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
Comment 1 Telesto 2019-06-02 13:44:22 UTC
Created attachment 151850 [details]
Example file
Comment 2 m.a.riosv 2019-06-02 14:09:27 UTC
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
Comment 3 Telesto 2019-06-03 07:50:21 UTC
Not sure if it's worth it, but bibisecting the point where the crashing stops/ slowness starts might give some insight