Bug 508591

SUMMARY
After running a routine system update, Chrome has started showing unbearable rendering and performance issues. The video in the attachment is a demonstration what I mean. Sometimes the browser is fine, but most of the time I can't even use it, which is quite the deal breaker as a full-time web developer.

I've already run through my extensions, even going as far as to wipe my Chrome configuration, hoping to resolve the problem that way. Whatever I do, I can't get it to go away. It's worth nothing though that I have not been able to reproduce this bug in the `chromium` RPM package, nor Microsoft Edge.

I tried googling this bug to try to find a solution myself, as I usually do, but I can't seem to find anyone else who has encountered this same problem. I'm also not aware if this is even the right place to post a bug like this, but I feel that you all might be able to at least point me in the right direction, perhaps even proposing some fixes. Any help is greatly appreciated.

STEPS TO REPRODUCE
It's hard for me to formulate an exact plan to reproduce the bug, it just happened out of nowhere. Watch the video in the attachments to understand what the bug is about, maybe it's familiar to one of you.

OBSERVED RESULT
An intermittently broken Chrome renderer, resulting in a rather unpleasant and unbearable experience.

EXPECTED RESULT
Proper functionality of Google Chrome, high performance as was present before, without any rendering issues

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 42 (WAYLAND)
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel: 6.14.11-300.fc42.x86_64 (tried older and newer kernels, no change)
Chrome Version 139.0.7258.127 (Official Build) (64-bit)

HARDWARE
AMD Ryzen 7 2700X
AMD Radeon RX 590 Series
MSI B350M motherboard

ADDITIONAL INFORMATION
Google Chrome was first installed using the RPM package google-chrome-stable, then reinstalled as a flatpak as a troubleshooting measure. This switch did not resolve the problem. A switch to Xorg has not been attempted, and I won't either, Chrome worked fine on Wayland before I updated my system, it has to work fine again on Wayland.