[Bug] Crash on Linux: SIGSEGV in gdk_window_end_draw_frame (libgdk-3) #2058

New issue

Closed

opened 2026-09-11 09:37:58 +00:00 by jvdongen · 0 comments

jvdongen commented

2026-09-11 09:37:58 +00:00

App: OciDeck 0.6.0 (AppImage)
OS: Arch Linux (rolling)
Desktop: Hyprland (Wayland) via UWSM
GTK: 3.24

Crash summary:
OciDeck segfaults reproducibly during normal use. It has crashed twice in ~40 minutes with identical stack traces. Both crashes occurred inside GTK3's drawing code.

Signal: SIGSEGV (SEGV_MAPERR)
Fault address: 0xffffffffffffffe4

Stack trace (main thread):
#0 0x00007f27d94f9c15 libgdk-3.so.0 + 0x32c15
#1 0x00007f27d9504fc2 libgdk-3.so.0 + 0x3dfc2
#2 gdk_window_end_draw_frame libgdk-3.so.0 + 0x3e0e3
#3 gtk_main_do_event libgtk-3.so.0 + 0x1f0a64
#4 ... libgdk-3.so.0
...
#16 g_main_context_iteration libglib-2.0.so.0
#17 g_application_run libgio-2.0.so.0
#18 main ocideck

Thread context:

Main thread handling GTK draw event
Background threads: Mesa/Gallium (Intel GPU), image loading (libglycin), Flutter engine workers

Reproducibility: 2/2 crashes today, identical stack.

What I was doing: Normal app usage; no specific trigger identified.

No OOM or resource exhaustion (32 GB RAM, 6 GB available).

App: OciDeck 0.6.0 (AppImage) OS: Arch Linux (rolling) Desktop: Hyprland (Wayland) via UWSM GTK: 3.24 Crash summary: OciDeck segfaults reproducibly during normal use. It has crashed twice in ~40 minutes with identical stack traces. Both crashes occurred inside GTK3's drawing code. Signal: SIGSEGV (SEGV_MAPERR) Fault address: 0xffffffffffffffe4 Stack trace (main thread): #0 0x00007f27d94f9c15 libgdk-3.so.0 + 0x32c15 #1 0x00007f27d9504fc2 libgdk-3.so.0 + 0x3dfc2 #2 gdk_window_end_draw_frame libgdk-3.so.0 + 0x3e0e3 #3 gtk_main_do_event libgtk-3.so.0 + 0x1f0a64 #4 ... libgdk-3.so.0 ... #16 g_main_context_iteration libglib-2.0.so.0 #17 g_application_run libgio-2.0.so.0 #18 main ocideck Register state at crash: rdi=0x0, suggesting a NULL pointer is being dereferenced in the drawing path. Thread context: - Main thread handling GTK draw event - Background threads: Mesa/Gallium (Intel GPU), image loading (libglycin), Flutter engine workers Reproducibility: 2/2 crashes today, identical stack. What I was doing: Normal app usage; no specific trigger identified. No OOM or resource exhaustion (32 GB RAM, 6 GB available).

jvdongen added the

bug

label

2026-09-11 09:37:58 +00:00