Bugzilla

I opened a few crashes to see what's going on, given this is spiking on Firefox. The crashes all originate from [`_gdk_wayland_display_queue_events()`](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/wayland/gdkeventsource.c?ref_type=heads#L208-243) or [`gdk_event_source_check()`](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/wayland/gdkeventsource.c?ref_type=heads#L94-127). In both cases the root cause is the same: something happened to the pipe that we use to connect to Wayland and we're crashing because of that.

I don't really see a pattern among the crashes, they seem to happen on different distros and different compositors. However the crashiness seems to have started in the nightly channel with buildid 20231018062241, so that's where I'd start to look at.

(Personal note: I can't help but be somewhat critical of a design that relies on a connection but apparently has now way to recover from errors with the connection itself)

I opened a few crashes to see what's going on, given this is spiking on Firefox. The crashes all originate from [`_gdk_wayland_display_queue_events()`](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/wayland/gdkeventsource.c?ref_type=heads#L208-243) or [`gdk_event_source_check()`](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/wayland/gdkeventsource.c?ref_type=heads#L94-127). In both cases the root cause is the same: something happened to the pipe that we use to connect to Wayland and we're crashing because of that.

~~I don't really see a pattern among the crashes, they seem to happen on different distros and different compositors. However the crashiness seems to have started in the nightly channel with buildid 20231018062241, so that's where I'd start to look at.~~

(Personal note: I can't help but be somewhat critical of a design that relies on a connection but apparently has now way to recover from errors with the connection itself)