Chrome/Chromium Wayland Performance Regression and DMA-BUF Failure on RTX 4060 Laptop GPU with Driver 580.126.09 (KDE Plasma 6)

System Information

  • GPU: NVIDIA GeForce RTX 4060 Laptop GPU

  • Driver: 580.126.09

  • CUDA: 13.0

  • Distribution: TUXEDO OS

  • Kernel: 6.17.0-119029-tuxedo

  • Desktop Environment: KDE Plasma 6

  • Session Type: Wayland

  • Browser: Google Chrome 148.0.7778.215

  • Vulkan: Available and functional

  • Hardware: Laptop with Intel iGPU and NVIDIA RTX 4060

Problem Summary

Chromium-based browsers exhibit severe performance issues under Wayland.

Observed behavior:

  • WebGL/WebGPU benchmarks are limited to approximately 1–2 FPS under the default configuration.

  • Firefox performs significantly better (~22 FPS).

  • Native Vulkan applications such as vkcube run smoothly, confirming that the NVIDIA driver and Vulkan stack are functioning correctly.

  • Chrome’s GPU process is launched with:

--render-node-override=/dev/dri/renderD128

where:

  • renderD128 = Intel GPU

  • renderD129 = NVIDIA RTX 4060

Chrome reports:

GL_RENDERER: ANGLE (Intel, Mesa Intel Graphics)

even though nvidia-smi shows Chrome attached to the NVIDIA GPU.

Additional Testing

Default Chrome

Chrome launches with:

--ozone-platform=wayland
–render-node-override=/dev/dri/renderD128

Result:

  • WebGL/WebGPU hardware acceleration reports enabled.

  • Extremely poor performance (~1–2 FPS).

Forcing NVIDIA Render Node

Chrome launched with:

--ozone-platform=wayland
–render-node-override=/dev/dri/renderD129

Result:

Chrome crashes with:

libwayland: importing the supplied dmabufs failed

and

‘–ozone-platform=wayland’ is not compatible with Vulkan

X11 Workaround

Chrome launched with:

--ozone-platform=x11
–render-node-override=/dev/dri/renderD129
–disable-features=Vulkan

Result:

  • Browser starts successfully.

  • Performance improves to approximately 23 FPS.

  • No immediate crash.

Verification

Native Vulkan test:

vkcube

Result:

  • Smooth rendering.

  • No stuttering.

  • Confirms NVIDIA Vulkan stack is healthy.

Question

Is this a known issue involving:

  • NVIDIA 580.126.09

  • Wayland DMA-BUF import

  • Explicit synchronization

  • Chromium render-node selection

and are there any recommended workarounds or patches available?

I can provide complete chrome://gpu output, nvidia-smi output, and additional logs if required.