Austin Shafer

Oh I forgot to mention, enabling `WAYLAND_DEBUG=1` for the logs is also helpful. Thanks, based on your log OBS has the same protocol error we should file an issue with...

What kernel version is this firefox bad fd crash with? Can you please provide details about that system? Note that 6.8.x kernels have some DRM syncobj fixes that help explicit...

Sorry for the late follow up, but can you please provide any details for how you triggered this crash? was this on startup or while performing some action?

We still haven't been able to reproduce this internally. Since the crash is happening in egl-wayland it would be very helpful if someone could build egl-wayland from source and get...

The issue with that protocol error on Vulkan is a fix we have internally which will be in a future release. I can't reproduce any issues on GL native wayland...

Those are pretty much the exact commands I used, except my build ended up being a release build so the binary was `examplesRelease`. I saw the window start, said it...

Are you sure bgfx is calling eglDestroySurface properly? I don't see any calls to `wp_linux_drm_syncobj_surface_v1_destroy` here (which we do in `wlEglDestroySurface` in egl-wayland to clean up) so it doesn't seem...

Based on your `__EGL_VENDOR_LIBRARY_FILENAMES` usages I'm guessing these logs are from using Vulkan correct? The "reusing a wl_surface" check we added to egl-wayland will obviously not catch any app issues...

What kernel version is this with? ekurzinger fixed some issues with `DRM_IOCTL_SYNCOBJ_TIMELINE_WAIT` that iirc could cause some hangs like this.

Then you should have Erik's patches. Sounds like this is most likely related to https://bugs.kde.org/show_bug.cgi?id=487728 which we have a fix for on the way.