Bug 786953 – random crash (SIGSEGV)

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 786953 - random crash (SIGSEGV)


Summary:	random crash (SIGSEGV)


Status:	RESOLVED OBSOLETE

Product:	gnome-software
Classification:	Applications
Component:	General
Version:	3.22.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Software maintainer(s)
QA Contact:	GNOME Software maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2017-08-29 03:55 UTC by Paul Wise
Modified:	2017-12-05 13:26 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
gdb backtrace of the crash (13.13 KB, text/plain) 2017-08-29 03:55 UTC, Paul Wise	Details

Description Paul Wise 2017-08-29 03:55:53 UTC

Created attachment 358648 [details]
gdb backtrace of the crash

I got a random crash (SIGSEGV) in gnome-software. I am using gnome-software 3.22.5-1 and GNOME 3.22 on Debian stretch. If the below gdb backtrace and the attached full gdb backtrace isn't useful, please close this bug.

Core was generated by `/usr/bin/gnome-software --gapplication-service'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 237900

#0 __GI___libc_free
at malloc.c line 2966
#0 __GI___libc_free
at malloc.c line 2966
#1 g_free
at ../../../../glib/gmem.c line 189
#2 g_error_free
at ../../../../glib/gerror.c line 491
#3 g_clear_error
at ../../../../glib/gerror.c line 674
#4 get_updates_historical_cb
at gs-update-monitor.c line 458
#5 g_task_return_now
at ../../../../gio/gtask.c line 1145
#6 complete_in_idle_cb
at ../../../../gio/gtask.c line 1159
#7 g_main_dispatch
at ../../../../glib/gmain.c line 3148
#8 g_main_context_dispatch
at ../../../../glib/gmain.c line 3813
#9 g_main_context_iterate
at ../../../../glib/gmain.c line 3886
#10 g_main_context_iteration
at ../../../../glib/gmain.c line 3947
#11 g_application_run
at ../../../../gio/gapplication.c line 2378
#12 main
at gs-main.c line 55

Comment 1 Richard Hughes 2017-12-05 11:52:18 UTC

Thanks for taking the time to report this.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and reopen this bug report. Thanks in advance!

Comment 2 Paul Wise 2017-12-05 13:17:43 UTC

Are you sure? I don't see any missing trace information in the trace nor the attachment. Even the glibc parts have proper trace info. The trace has all threads in it. This isn't gnome-shell so there is no JavaScript backtrace to get.

Comment 3 Richard Hughes 2017-12-05 13:21:46 UTC

Well, I reviewed the bt, and I couldn't seem how this could happen: g_clear_error() is the crash, which can't really happen looking at the code. Can you reproduce this again?

Comment 4 Paul Wise 2017-12-05 13:26:27 UTC

The trace seemed like a use-after-free to me. It was a random crash that happened one day, so no way to reproduce. gnome-software is at 3.26 now, so lets mark the crash as obsolete.