GTK4.16 spontaneous no GLX or EGL context

[yvs2014]

Hi everyone,

is there a way to trace/debug what can cause sometimes gtk4 app to crash using GTK4.16? Before (with 4.14 4.15) it was enough to set previous gsk renderers to get it to work smoothly, with 4.16 it starts to crash (from time to time) even with GSK_RENDERER=gl, like

../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
IOT instruction (core dumped)  pingpath -R 1.1.1.1

p.s. env: gtk4.16.1 mesa24.2.2

[lb90]

Hi @yvs2014, could you open an issue at Issues · GNOME / gtk · GitLab?

[yvs2014]

To do that I need some minimally reproducible code (it needs a lot to reduce all code down), that I don’t have. Only come up (in gdb) to point gtk_widget_unrealize() and g_signal_emit(widget, widget_signals[UNREALIZE], 0) point when it happens (in app using gtk_gl_area).

update: found a workaround in my case: remove(detach) widget with gl_area before exit, “no GLX/EGL context” was at application exit when widget with gl_area was active.