https://bugs.kde.org/show_bug.cgi?id=520869
Bug ID: 520869
Summary: Wayland DMA-BUF import failure and severe Chromium
performance degradation when using NVIDIA render node
on KDE Plasma 6
Classification: Plasma
Product: kwin
Version First master
Reported In:
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
I am experiencing a Wayland graphics issue involving KWin, Chromium, and NVIDIA
GPUs.
System configuration:
* Distribution: TUXEDO OS
* Desktop Environment: KDE Plasma 6
* Window Manager/Compositor: KWin
* Session Type: Wayland
* GPU: NVIDIA GeForce RTX 4060 Laptop GPU
* NVIDIA Driver: 580.126.09
* Browser: Google Chrome 148.0.7778.215
Problem:
Chromium-based browsers exhibit severe graphics performance problems under
Wayland. WebGL/WebGPU workloads run at approximately 1–2 FPS despite hardware
acceleration being reported as enabled.
During troubleshooting I discovered that Chrome launches its GPU process using
the Intel render node:
--render-node-override=/dev/dri/renderD128
while the NVIDIA GPU is available as:
/dev/dri/renderD129
When Chrome is forced to use the NVIDIA render node under Wayland:
google-chrome-stable
--ozone-platform=wayland
--render-node-override=/dev/dri/renderD129
the browser fails with the following error:
libwayland: importing the supplied dmabufs failed
and terminates.
Additional testing:
* Native Vulkan applications such as `vkcube` work correctly and render
smoothly.
* NVIDIA drivers appear to be functioning normally.
* Firefox performs significantly better than Chromium.
* Running Chromium under X11 with:
google-chrome-stable
--ozone-platform=x11
--render-node-override=/dev/dri/renderD129
--disable-features=Vulkan
allows the browser to start and improves performance considerably.
Expected behavior:
KWin should successfully handle DMA-BUF imports and Chromium should be able to
use the NVIDIA render node under Wayland without crashes or severe performance
degradation.
Actual behavior:
Forcing Chromium to use the NVIDIA render node under Wayland causes DMA-BUF
import failures and browser startup problems, while the default configuration
results in extremely poor WebGL/WebGPU performance.
Because the issue appears specifically when KWin/Wayland attempts to import
buffers from the NVIDIA rendering path, I am reporting this here in case it is
related to KWin's Wayland compositor, DMA-BUF handling, or explicit
synchronization behavior.
--
You are receiving this mail because:
You are watching all bug changes.
