Renderer process terminated on Mesa versions 25.2.0 and above

[jameshilliard]

I'm seeing a cog renderer crash after buildroot's mesa3d was bumped to version 25.2.2 from 25.1.8, I'm also seeing it on buildroot's master where the mesa3d package is at version 25.2.5

I'm seeing this in the logs:

Renderer process terminated and failed to recover within 1000ms
<> Crash!: The renderer process crashed. Reloading the page may fix intermittent failures.
libEGL warning: failed to get driver name for fd -1
libEGL warning: MESA-LOADER: failed to retrieve device information
libEGL warning: failed to get driver name for fd -1
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Could not create WPE EGL display: EGL_NOT_INITIALIZED. Aborting...

Does anyone know what might be causing this?

[lawik]

We've hit this with our project as well. Reverting to 25.1.9 seems to work.

Weston starts fine. Cog does the above error. Still a problem on mesa 25.2.7.

[fhunleth]

I don't have a fix, but I can narrow it down a slight bit more. Mesa3D 25.2.0 is the first version to fail for me. The current latest version, Mesa3D 25.3.3, didn't work either.

I was using WPEBackend-fdo 1.16.0. Updating to 1.16.1 did not fix the issue for me. I was hopeful due to the changelog entry in 1.16.1 that referred to supporting newer Mesa versions, but that must be something else.

[jameshilliard]

So first known bad version is 25.2.0 and last known working is 25.1.9 I guess? I guess maybe need to bisect mesa commits between those tags?

[MagneFire]

For what it's worth, this can also be reproduced with MiniBrowser.

[MagneFire]

Using the WPEPlatform API (instead of the fdo backend) with the MiniBrowser solves the issue for me.

So perhaps it has something to do with the fdo backend after all?

[d99roric]

The issue happens if a recent mesa is built without the legacy wl_drm support. (-Dlegacy-wayland=bind-wayland-display)

Without wl_drm mesa will not get the hint of device name to use...it does not get the main_device call on the zwp_linux_dmabuf_v1 interface.

[jameshilliard]

The issue happens if a recent mesa is built without the legacy wl_drm support. (-Dlegacy-wayland=bind-wayland-display)

I can confirm this fixes the issue, thanks.

Without wl_drm mesa will not get the hint of device name to use...it does not get the main_device call on the zwp_linux_dmabuf_v1 interface.

Hmm, I guess this is probably an issue in WPEBackend-fdo then? I wonder what the proper fix for this issue is.