When the resolution of the display on GNOME 44 is set to 3840 × 2160, LibreOffice Writer's scrolling becomes choppy and laggy.
As the resolution is lowered to something like 1440p, the effect diminishes. The lower the resolution, the less the effect.
I compared it to Firefox, which is able to scrolling very smoothly without dropped frames/lag on the same hardware. I tested several other applications (Audacious, GNOME Terminal, GNOME Text Editor, Element, and Telegram, and none of them have choppy/laggy scrolling at 4k on my hardware).
Turning on or off Java in the preferences makes no difference.
I've only confirmed this in LibreOffice writer, but I suspect the issue affects all of the entire LibreOffice suites.
I'm guessing LibreOffice struggles with higher resolutions either due to a bug, inefficiency of some kind, or possible memory leak.
Running radeontop shows a spike in GPU clock and memory usage. CPU jumps when scrolling at this resolution as well, more so than 1440p or 1080p.
Changing refresh rate to something lower than 100hz does not seem to help the issue. Even at 60hz, LibreOffice is still noticeably slower/laggier/choppier than every other application on the same hardware when scrolling.
Note that while typing, key presses take slightly longer to register. Sometimes entire phrases will take seconds or more to register and print to the screen, though this is rare. Text input lags considerably as resolution of the desktop increases. This problem does not persist in other applications as mentioned above.
Steps to Reproduce:
1. Change resolution of GNOME desktop in Fedora 38 to 3840 × 2160.
2. Restart LibreOffice writer.
3. Scroll any document that is sufficiently long enough (a page or more, for example).
Choppy/laggy scrolling performance.
Smooth scrolling and no dropped frames/lag the same as resolutions lower than 3840 × 2160.
User Profile Reset: Yes
I was able to reproduce this bug on Linux Mint 21.1 through Cinnamon. The same issue happened when I was using i3-wm on Linux Mint 21.1.
Using Wayland or X.org doesn't seem to make much of a difference.
I will be adding a video showing the lag sometime today or tomorrow.
Look the same as bug 154602. Let's mark it as duplicate
*** This bug has been marked as a duplicate of bug 154602 ***