SUMMARY Launching chromium or any chromium based application with "--enable-features=UseOzonePlatform --ozone-platform=wayland" I got very poor performance on KDE Wayland. Chromium does not match monitors refresh rate and FPS is very low around 48-58 fps. On GNOME Chromium is beautifully smooth. I tried run Chromium both on KDE, GNOME on OpenSUSE, Manjaro. Chromium was always laggy on KDE, smooth on GNOME. STEPS TO REPRODUCE 1. Launch chromium with native Wayland support "--enable-features=UseOzonePlatform --ozone-platform=wayland" EXPECTED RESULT Gain performance by running Chromium on native Wayland support. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2
Can you please check if changing the latency policy (in system settings) to "prefer smoothest animations" fixes the issue?
Created attachment 140187 [details] Chromium SIGBUS error
(In reply to Vlad Zahorodnii from comment #1) > Can you please check if changing the latency policy (in system settings) to > "prefer smoothest animations" fixes the issue? Nothing changed. Also I got some SIGBUS errors in Chromium.
(In reply to Vlad Zahorodnii from comment #1) > Can you please check if changing the latency policy (in system settings) to > "prefer smoothest animations" fixes the issue? Running Firefox on Wayland will match my monitor refresh rate (144 hz) on GNOME 40 and KDE Plasma 5.22.3. https://webglsamples.org/aquarium/aquarium.html I get stable 144 fps. Running Chrome on Wayland will not match my monitor refresh rate and I got around 55 fps on https://webglsamples.org/aquarium/aquarium.html not even stable 60 This does not happen on GNOME 40. Log from Chrome: [27275:27275:0728/020403.343050:ERROR:cursor_loader.cc(107)] Failed to load a platform cursor of type kNull [27316:27316:0728/020403.368223:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is egl [27316:27316:0728/020403.371236:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [27316:27316:0728/020436.766161:ERROR:gles2_cmd_decoder.cc(8216)] [.WebGL-0xe023ba22100]GL ERROR :GL_INVALID_OPERATION : glClear: can't be called on integer buffers [27316:27316:0728/020437.059872:ERROR:gles2_cmd_decoder.cc(10718)] [.WebGL-0xe023ba22100]RENDER WARNING: there is no texture bound to the unit 1 [27316:27316:0728/020437.104605:ERROR:gles2_cmd_decoder.cc(8216)] [.WebGL-0xe023ba22100]GL ERROR :GL_INVALID_OPERATION : glClear: can't be called on integer buffers [27316:27316:0728/020437.106266:ERROR:gles2_cmd_decoder.cc(10738)] [.WebGL-0xe023ba22100]GL ERROR :GL_INVALID_OPERATION : glDrawArrays: Texture bound to texture unit 1 with internal format GL_RG32UI is not compatible with sampler type GL_SAMPLER_2D Can I provide some additional information?
I am experiencing the same issue. KWin 5.24.5 Version 101.0.4951.54 (Official Build) (64-bit)
It's possible that supporting explicit sync and/or presentation timing could resolve some of the issues, but ultimately it's a chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1310539
Is there a specific reason why this issue does not occur on GNOME?
Chrome for an example works at both 144hz/165hz with a Wayland compositor such as Wayfire or Sway. This however seems capped at 58-60fps on Plasma under Wayland. My monitor has a feature to check the current framerate, and it shows 144hz/165hz (I tested both HDMI (max is 144hz for my monitor) Displayport (max is 165hz for my monitor) for the desktop. glxgears shows the correct framerate as well. I have a `Navi 10 Radeon RX 5600XT` graphics card, tried both Mesa 22.2.1 and mesa-git (c1cb7506bb39843384b5b6114cd8690a38655ef3, latest as of Monday, 17 October 2022).