After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789278 - crash (SIGSEGV) on exit
crash (SIGSEGV) on exit
Product: totem
Classification: Core
Component: general
Other All
: Normal critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Reported: 2017-10-21 03:23 UTC by Paul Wise
Modified: 2018-05-24 11:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

gdb backtrace of the crash (17.80 KB, text/plain)
2017-10-21 03:23 UTC, Paul Wise

Description Paul Wise 2017-10-21 03:23:22 UTC
Created attachment 361997 [details]
gdb backtrace of the crash

I got a crash (SIGSEGV) in totem on exit. I am using totem 3.26.0-1 and GNOME 3.22 on Debian buster. If the below gdb backtrace and the attached full gdb backtrace isn't useful, please close this bug.

Core was generated by `totem <removed>'.
Program terminated with signal SIGSEGV, Segmentation fault.
  • #0 __run_exit_handlers
    at exit.c line 55
  • #0 __run_exit_handlers
    at exit.c line 55
  • #1 __GI_exit
    at exit.c line 105
  • #2 totem_object_wait_force_exit
    at ../src/totem-object.c line 1306
  • #3 g_thread_proxy
    at ../../../../glib/gthread.c line 784
  • #4 start_thread
    at pthread_create.c line 333
  • #5 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 97

Comment 1 Bastien Nocera 2017-10-21 12:05:09 UTC
It gets to that point because the program is hung. I think it doesn't like exit() being called from a thread, but that only happens when the main thread is stuck. I don't see where in the backtrace it would do that though.
Comment 2 GNOME Infrastructure Team 2018-05-24 11:26:53 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: