Random segmentation fault while browsing inside huge tar file

Bug #1889139 reported by Alexandre-Xavier Labonté-Lamoureux
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
engrampa (Ubuntu)
New
Undecided
Unassigned

Bug Description

Engrampa randomly segfaults while I browse the files in a huge tar file. More specifically, the SIGSEGV happens when I open a folder inside the tar file.

These are the packages that I have installed:
* engrampa_1.24.0-2_amd64.deb
* engrampa-common_1.24.0-2_all.deb

(I'm on Ubuntu 20.04, I built these packages from the source so I could have the debugging symbols. I followed the instructions from here: https://wiki.debian.org/HowToGetABacktrace)

Here's the GDB output with the debug symbols:

Thread 1 "engrampa" received signal SIGSEGV, Segmentation fault.
gdk_window_is_destroyed (window=0x1) at ../../../../gdk/gdkwindow.c:2341
2341 ../../../../gdk/gdkwindow.c: No such file or directory.
(gdb) bt
#0 gdk_window_is_destroyed (window=0x1) at ../../../../gdk/gdkwindow.c:2341
#1 0x00007f6323fc3a74 in gtk_get_event_widget (event=event@entry=0x55adf2d83640) at ../../../../gtk/gtkmain.c:2562
#2 0x00007f6324106b93 in gtk_widget_event_internal (event=0x55adf2d83640, widget=0x55adf2c5c400) at ../../../../gtk/gtkwidget.c:7692
#3 gtk_widget_event_internal (widget=0x55adf2c5c400, event=0x55adf2d83640) at ../../../../gtk/gtkwidget.c:7677
#4 0x00007f6323fc2128 in propagate_event_up (topmost=<optimized out>, event=<optimized out>, widget=0x55adf2c5c400) at ../../../../gtk/gtkmain.c:2597
#5 propagate_event (widget=<optimized out>, event=0x55adf2d83640, captured=<optimized out>, topmost=0x0) at ../../../../gtk/gtkmain.c:2700
#6 0x000055adf167cf9d in egg_tree_multi_drag_button_release_event (widget=0x55adf2c5c400, event=0x55adfbb75220, data=0x0) at eggtreemultidnd.c:205
#7 0x00007f632415c4fb in _gtk_marshal_BOOLEAN__BOXED
    (closure=0x55adfb1c5530, return_value=0x7ffe632b1320, n_param_values=<optimized out>, param_values=0x7ffe632b1380, invocation_hint=<optimized out>, marshal_data=<optimized out>) at gtkmarshalers.c:83
#8 0x00007f632387c802 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007f6323890814 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007f632389b45d in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007f632389c0d3 in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007f6324106c23 in gtk_widget_event_internal (event=0x55adfbb75220, widget=0x55adf2c5c400) at ../../../../gtk/gtkwidget.c:7808
#13 gtk_widget_event_internal (widget=0x55adf2c5c400, event=0x55adfbb75220) at ../../../../gtk/gtkwidget.c:7677
#14 0x00007f6323fc2128 in propagate_event_up (topmost=<optimized out>, event=<optimized out>, widget=0x55adf2c5c400) at ../../../../gtk/gtkmain.c:2597
#15 propagate_event (widget=<optimized out>, event=0x55adfbb75220, captured=<optimized out>, topmost=0x0) at ../../../../gtk/gtkmain.c:2700
#16 0x00007f6323fc43db in gtk_main_do_event (event=0x55adfbb75220) at ../../../../gtk/gtkmain.c:1920
#17 gtk_main_do_event (event=<optimized out>) at ../../../../gtk/gtkmain.c:1690
#18 0x00007f6323cacf79 in _gdk_event_emit (event=event@entry=0x55adfbb75220) at ../../../../gdk/gdkevents.c:73
#19 0x00007f6323ce0106 in gdk_event_source_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../../../../../gdk/x11/gdkeventsource.c:367
#20 0x00007f6323790fbd in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f6323791240 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f63237912e3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f63239aafd5 in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#24 0x000055adf16c0ca2 in main (argc=1, argv=0x7ffe632b1a08) at main.c:353

Tags: focal
Revision history for this message
Alexandre-Xavier Labonté-Lamoureux (alexandrexavier) wrote :
Norbert (nrbrtx)
tags: added: focal
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.