Summary: | Chromium stuck at 60 fps | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Ondřej Niesner <ondra.niesner> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | david, kde, miranda, nate, xaver.hugl |
Priority: | NOR | ||
Version First Reported In: | 5.24.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ondřej Niesner
2022-03-18 02:21:37 UTC
Since you're using Chromium in native Wayland mode, I guess it's not an example of Bug 449958. 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 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) Oops, sorry, wrong issue. I can't delete comments *** Bug 480436 has been marked as a duplicate of this bug. *** Looks like the correct issue to me, sort of :) |