Created attachment 186471 [details]
Small CSV file that exhibits the bug on my computer
When holding down navigation keys to quickly scroll through the document, scroll is very laggy and even continues for a while after I've released the key. On 1920x1080, only left/right is laggy, but on 4K external monitor it's much worse overall and up/down is affected too.
I'm attaching a sample document, it's barely 200x30 cells big.
Fedora Linux 37
Lenovo ThinkPad P1 Gen 3
Intel® Core™ i9-10885H × 16
Mesa Intel® UHD Graphics (CML GT2)
I notice a slight difference when I use GTK3 and move with the arrows (pressing and holding) left and right through the cells with content. I don't have a 4K screen.
The difference is too subtle for me to effectively perform a bibisect, so I suggest that you try it with the 7.5 repository (it seems to not be in 7.4, but you can try it as well): https://wiki.documentfoundation.org/QA/Bibisect/Linux
The slowness might be related to accessibility as it works only with GTK3 for now. I see in the console sometimes:
** (soffice:73597): WARNING **: 14:20:09.963: atk-bridge: get_device_events_reply: unknown signature
Arch Linux 64-bit, X11
Version: 220.127.116.11 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: CL threaded
Installed 18.104.22.168 from an RPM on the official website, the bug persists :( exactly the same as reported AFAIK
If you need help in bibisecting, email me and I can guide you in a call.
Oh I see, you would like me to bibisect on my machine? I'll try and find the time then
*** Bug 155217 has been marked as a duplicate of this bug. ***
*** Bug 153007 has been marked as a duplicate of this bug. ***
*** Bug 155375 has been marked as a duplicate of this bug. ***
There are some bug reports about performance problems with Wayland. Others like bug 155375 comment 0 report no difference between x.org or Wayland. So might be caused by a 4k monitor or Wayland backend, or both.. Or maybe even something else
(In reply to Telesto from comment #8)
> There are some bug reports about performance problems with Wayland. Others
> like bug 155375 comment 0 report no difference between x.org or Wayland. So
> might be caused by a 4k monitor or Wayland backend, or both.. Or maybe even
> something else
I will test the 4k performance problem on Xorg sometime this week. I don't notice a difference between 1080p/1440p Wayland and Xorg - they're both very responsive. The problem seems to happen when the resolution is switched to something like 4k on Wayland.
We'll see if the problem persists on Xorg.
Played with LibreOffice (writer) at 4k on Xorg and i3wm. Same thing seems to happen. CPU usages spikes to 50% plus on a single thread/core for some reason.
Scrolling other applications like Firefox at 4k for example doesn't seem to push any particular CPU thread drastic usage levels.