View Issue Details

IDProjectCategoryView StatusLast Update
0006165DarkRadiantGUIpublic28.03.2023 03:18
Reporterjonri Assigned To 
Status acknowledgedResolutionopen 
PlatformLinuxOSFlatpak, Arch 
Product Version3.6.0 
Summary0006165: Crash/exit when launching some dialogs
DescriptionLaunching a new 2D view, TexTool, or Light window all cause a crash for me on my laptop and an immediate exit with code 1 on my desktop.
Datiswous reported junk rendering in some of the same windows, which might or might not be related. Interestingly, the Light window actually displays and the area where you choose your material says "Loading Resources" before it stops.

Steps To Reproduce1. Open DarkRadiant
2. Open a new 2D view, TexTool window, or Light window
Additional InformationThe stack trace comes from deep within wx and gtk, none of our own code is in the trace:

Thread 1 "darkradiant" received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff7ce2def in g_log_structured_array () from /usr/lib/x86_64-linux-gnu/
(gdb) bt
#0 0x00007ffff7ce2def in g_log_structured_array () at /usr/lib/x86_64-linux-gnu/
0000001 0x00007ffff7ce2fb6 in g_log_structured_standard () at /usr/lib/x86_64-linux-gnu/
0000002 0x00007ffff57a6fc3 in _gdk_x11_display_error_event () at /usr/lib/x86_64-linux-gnu/
0000003 0x00007ffff57b4cd3 in gdk_x_error () at /usr/lib/x86_64-linux-gnu/
0000004 0x00007ffff5234d1b in _XError () at /usr/lib/x86_64-linux-gnu/
0000005 0x00007ffff52315df in handle_error () at /usr/lib/x86_64-linux-gnu/
0000006 0x00007ffff5231685 in handle_response () at /usr/lib/x86_64-linux-gnu/
0000007 0x00007ffff5232172 in _XEventsQueued () at /usr/lib/x86_64-linux-gnu/
#8 0x00007ffff52354bd in _XGetRequest () at /usr/lib/x86_64-linux-gnu/
0000009 0x00007ffff2426285 in XRenderFillRectangles () at /usr/lib/x86_64-linux-gnu/
0000010 0x00007ffff5638ffd in fill_boxes () at /usr/lib/x86_64-linux-gnu/
0000011 0x00007ffff561ba26 in clip_and_composite_boxes.part () at /usr/lib/x86_64-linux-gnu/
0000012 0x00007ffff561bf25 in _cairo_traps_compositor_fill () at /usr/lib/x86_64-linux-gnu/
0000013 0x00007ffff55bf3d2 in _cairo_compositor_fill () at /usr/lib/x86_64-linux-gnu/
0000014 0x00007ffff56404a0 in _cairo_xlib_surface_fill () at /usr/lib/x86_64-linux-gnu/
0000015 0x00007ffff56134bb in _cairo_surface_fill () at /usr/lib/x86_64-linux-gnu/
0000016 0x00007ffff55c821c in _cairo_gstate_fill () at /usr/lib/x86_64-linux-gnu/
0000017 0x00007ffff55c0ece in _cairo_default_context_fill () at /usr/lib/x86_64-linux-gnu/
0000018 0x00007ffff56213bf in cairo_fill () at /usr/lib/x86_64-linux-gnu/
0000019 0x00007ffff5b29ba0 in render_frame_fill () at /usr/lib/x86_64-linux-gnu/
0000020 0x00007ffff5b29fb2 in render_border () at /usr/lib/x86_64-linux-gnu/
0000021 0x00007ffff5b2b05f in gtk_css_style_render_border () at /usr/lib/x86_64-linux-gnu/
0000022 0x00007ffff59db5e2 in gtk_css_gadget_draw () at /usr/lib/x86_64-linux-gnu/
0000023 0x00007ffff5b37725 in gtk_scrolled_window_draw () at /usr/lib/x86_64-linux-gnu/
0000024 0x00007ffff5c1395c in gtk_widget_draw_internal () at /usr/lib/x86_64-linux-gnu/
0000025 0x00007ffff59d0226 in gtk_container_propagate_draw () at /usr/lib/x86_64-linux-gnu/
0000026 0x00007ffff5a4bc49 in gtk_fixed_draw () at /usr/lib/x86_64-linux-gnu/
TagsNo tags attached.




18.02.2023 19:57

developer   ~0015955

I started looking at this one again, and I can get the Light window to display if I remove the TexturePreviewCombo from the bottom of the MaterialSelector. I doubt that widget itself is directly to blame since it doesn't factor into the other two panels that still crash, but if I can track down which exact part of the TexturePreviewCombo is causing the issue maybe the same pattern will appear in the others.


28.03.2023 03:18

developer   ~0015980

Darkradiant purposely suppresses the GTK log messages, I turned this off to get more information:

The program 'darkradiant' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 27492 error_code 3 request_code 148 (unknown) minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I haven't gotten anywhere useful with its debugging suggestion, but I did try running in a Wayland session and noticed that this crash does not happen at all. There were some other warnings about negative sizes, so now I'm wondering if it's a UI layout issue of some sort, or maybe an issue with AUI.

Issue History

Date Modified Username Field Change
15.11.2022 04:07 jonri New Issue
17.11.2022 04:05 greebo Status new => acknowledged
18.02.2023 19:57 jonri Note Added: 0015955
28.03.2023 03:18 jonri Note Added: 0015980