Bug 451639 - Chromium stuck at 60 fps
Summary: Chromium stuck at 60 fps
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.24.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-18 02:21 UTC by Ondřej Niesner
Modified: 2024-01-28 20:22 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ondřej Niesner 2022-03-18 02:21:37 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Run "chromium --ozone-platform=wayland" with high refresh rate monitor.
 
OBSERVED RESULT
FPS are going down when using Chromium with higher refresh rate. Even with like 75 hz scrolling is not smooth. I tried to set my monitor to different refresh rate and this what I measured. It's really weird. 
FPS were measured from testufo.com 
Chromium with 
60 hz = 60 fps.
75 hz = 75 fps
100 hz = 100 fps
120 hz = 58 fps
144 hz = 58 fps

I tested Chromium on GNOME and Sway and I have no issues at all. It was running smoothly. I have this problem only on KDE. I personally don't use Chromium browser but this affects all programs that are running on Chromium.

EXPECTED RESULT
Run Chromium smoothly on Wayland with higher refresh rate.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.16.14-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series
Comment 1 Nate Graham 2022-03-26 03:35:29 UTC
Since you're using Chromium in native Wayland mode, I guess it's not an example of Bug 449958.
Comment 2 Zamundaaa 2022-03-26 20:52:09 UTC
Like in the bug report about Xwayland, I assume this is an upstream bug - the 58Hz thing is especially suspicious.
It is possible that we could work around it by (finally) supporting presentation-time (which Sway and GNOME do), but I think it's still a bug that things don't work correctly without it.

I opened a bug for chromium to track this there, at least until more information is found: https://bugs.chromium.org/p/chromium/issues/detail?id=1310539
Comment 3 Willian 2024-01-28 19:53:26 UTC
Found the issue: the fps is only limited if I set adaptive sync to "Always". Is this expected?

I'm using this option because "Automatic" and "Never" at 165hz causes flickering in my display (not sure if this is supposed to be another issue itself)
Comment 4 Willian 2024-01-28 19:55:50 UTC
Oops, sorry, wrong issue. I can't delete comments
Comment 5 Zamundaaa 2024-01-28 20:22:35 UTC
*** Bug 480436 has been marked as a duplicate of this bug. ***
Comment 6 Zamundaaa 2024-01-28 20:22:46 UTC
Looks like the correct issue to me, sort of :)