https://bugs.documentfoundation.org/show_bug.cgi?id=152911
--- Comment #129 from Gauthier <[email protected]> --- (In reply to Michael Weghorn from comment #125) > (In reply to Guido Iodice from comment #124) > > Although the bug may also be caused by Qt, which proves to be very slow on > > Wayland, even with the optimisations of the patch linked above, it is fair > > to say that this bug is present in LibreOffice olny. I use KDE, so I use a > > lot of Qt applications and no other Qt application has problems with > > scrolling. So I think something can be done on the LO side. > > Sure, I expect that e.g. document rendering in Writer is more complex (and > expensive in terms of CPU load) than what most other Qt applications do, and > profiling and trying to optimize that could be another non-trivial approach > to pursue. It's always worth looking at all layers involved. It "just" needs > somebody to do the work. (In reply to fv905co2k from comment #128) > (In reply to Guido Iodice from comment #124) > > (In reply to Michael Weghorn from comment #123) > > > (In reply to Michael Weghorn from comment #12) > > > > Created attachment 192316 [details] > > > > Hotspot flamegraph of scrolling using scrollbar w/ qt6 on Wayland > > > > > > Just another idea to keep in mind: Looking at that flamegraph again, it > > > can > > > be seen that the vcl ScollBar's mouse event handling is involved. Whether > > > or > > > not using a native QScrollBar instead would improve the situation is > > > unclear, but might generally be worth a try at least if Qt >= 6.11 isn't > > > going to fully resolve the situation. It depends on quite some other > > > things > > > to be done first in the context of tdf#130857 however. > > > > Although the bug may also be caused by Qt, which proves to be very slow on > > Wayland, even with the optimisations of the patch linked above, it is fair > > to say that this bug is present in LibreOffice olny. I use KDE, so I use a > > lot of Qt applications and no other Qt application has problems with > > scrolling. So I think something can be done on the LO side. > > This. > Optimization on QT6 can be beneficial, but the issue lies within > LibreOffice, as it's the only application experiencing this problem. > > My solution was to start using OnlyOffice while waiting for the bug to be > fixed. To add to this: While @Michael has got a good point in terms of LO being more heavy on rendering than many other apps, the fact that this issue occurs even on an empty document (either an empty spreadsheet or an empty writer document where you just create lots of blank pages and then scroll through) really feels like there is something going wrong that is quite specific to LO. -- You are receiving this mail because: You are the assignee for the bug.
