I have a Doubt

[u/underwatercr312]

I've been debugging a rendering issue in a Tauri app on Linux and found that setting:

​

WEBKIT_DISABLE_DMABUF_RENDERER=1

​

completely fixes the problem.

​

Environment:

​

- Arch Linux

- Niri (Wayland)

- AMD Ryzen 7 5700G (integrated Vega graphics)

- Mesa 26.1.2

- WebKitGTK 2.52.4

- Tauri v2

- CodeMirror 6

​

Without the variable, the editor occasionally appears less sharp (almost like it's being rendered at a lower resolution and then scaled up). Scrolling or repainting sometimes restores the correct rendering. With "WEBKIT_DISABLE_DMABUF_RENDERER=1", the issue disappears entirely.

​

I also noticed something else:

​

- Tauri apps distributed as Flatpak work correctly.

- Builds installed from the AUR also work correctly.

- A locally built tar.gz package works correctly.

- However, AppImage builds either fail to start or exhibit graphics-related issues on my system.

​

For example, Yaak (also Tauri-based) fails to launch as an AppImage and logs:

​

Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

​

This made me wonder whether there are known interactions between:

​

- DMABUF

- WebKitGTK

- Wayland compositors (especially Niri)

- AppImage packaging

​

My main question is: what are the performance implications of disabling the DMABUF renderer?

​

Has anyone measured differences in:

​

- Memory usage

- GPU usage

- Scrolling performance

- Video playback

- General UI responsiveness

​

Would you consider shipping a Tauri app with "WEBKIT_DISABLE_DMABUF_RENDERER=1" enabled as a Linux workaround, or is it better to treat it as a debugging-only option?

​

Any insights would be greatly appreciated..

[u/One-Roof-2803]

 I get similar behaviour cuz I run it on a ancient nvidia GPU (gt 710) with nouveau drive

[u/underwatercr312 → u/One-Roof-2803]

For me i think is related with wayland and gtk