GNOME Bugzilla – Bug 612363
empathy crashed with SIGSEGV in g_closure_invoke()
Last modified: 2011-08-29 10:12:28 UTC
Originally reported at: https://bugs.launchpad.net/bugs/527296 Binary package hint: empathy received a message from a contact and viewed in through the message indicator applet. shortly afterwards, empathy froze for a second or two and then crashed. looks like a bunch of karmic bugs w/ similar crash, but this is w/ latest lucid package, so filing new bug. ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Wed Feb 24 11:45:30 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113) NonfreeKernelModules: nvidia Package: empathy 2.29.91-1ubuntu1 ProcCmdline: empathy ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SegvAnalysis: Segfault happened at: 0x45254c: mov 0x68(%rbx),%edi PC (0x0045254c) ok source "0x68(%rbx)" (0x00000068) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () g_closure_invoke () ?? () from /usr/lib/libgobject-2.0.so.0 g_signal_emit_valist () g_signal_emit () from /usr/lib/libgobject-2.0.so.0 Title: empathy crashed with SIGSEGV in g_closure_invoke() Uname: Linux 2.6.32-14-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
the following sequence of events seems to trigger this crash very often: 0) double click a contact to open a new chat window 1) try to paste a url by middle clicking, where the selection is actually on another machine sharing mouse/keyboard through synergy 2) nothing shows up in chat window, so middle click again and see the url show up, and press enter to send msg w/ url in it 3) close chat window 4) wait some time, get the crash not sure how synergy-specific the paste issue is, or if its even related? but seems to trigger it quite effectively.
Could you please build empathy master and try to get a better trace? Thanks for taking the time to report this bug. 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 http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
does the trace in the linked launcpad bug help, or do you still need a new trace? http://launchpadlibrarian.net/39790683/Stacktrace.txt http://launchpadlibrarian.net/39790684/ThreadStacktrace.txt
+ Trace 220908
Stack trace seems wrong.
+ Trace 220996
This function is not localised at line 311. I'd be intersted in having a proper trace from master (Ubuntu used to introduce weird crashes because of their patch and I'm a bit tired of wasting time tracking them).
ok, reproduced on master, hopefully with all the information you need: on paste, i get a few thousand lines of: error: line 53473: bad flag alias index: 0 error: line 53473: bad flag vector alias error: line 53474: bad flag alias index: 0 error: line 53474: bad flag vector alias error: line 53475: bad flag alias index: 0 error: line 53475: bad flag vector alias error: line 53476: bad flag alias index: 0 error: line 53476: bad flag vector alias in the console, followed by: ** Message: console message: undefined @1: ReferenceError: Can't find variable: scrollToBottom [New Thread 0x7fffdb5d1710 (LWP 13491)] [Thread 0x7fffdb5d1710 (LWP 13491) exited] (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 1447906560 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 2737 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 2130896645 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 1447906628 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 134217728 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: -1274884859 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 1447906628 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 134217728 (empathy:13457): Gdk-WARNING **: /build/buildd/gtk+2.0-2.19.7/gdk/x11/gdkproperty-x11.c:325 invalid X atom: -368921851 Program received signal SIGSEGV, Segmentation fault. chat_composing_start (buffer=0xb151b0, chat=0xc170c0) at empathy-chat.c:343 343 if (priv->composing_stop_timeout_id) { (gdb) bt
+ Trace 220997
Thread 1 (Thread 0x7ffff7fb3820 (LWP 13457))
Great thanks! Could you test with this branch and see if that help: http://git.collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/paste-crash-612363
applied the latest diff to master, and don't get the crash anymore. still get a little bit of a freeze while the few thousand lines of: error: line 53473: bad flag alias index: 0 error: line 53473: bad flag vector alias are being output, and still the weird first-paste doesn't work issue (though now i've noticed that the paste does eventually happen if the chat window is left open...)
I doubt those are related.
Created attachment 156719 [details] [review] http://git.collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/paste-crash-612363 libempathy-gtk/empathy-chat.c | 7 ++----- 1 files changed, 2 insertions(+), 5 deletions(-)
Reviewed by Danielle. Let's merge it after the hard code freeze or before if accepted by the RT.
(In reply to comment #8) > I doubt those are related. seems to be related in that I believe (from behavior, not from understanding the code) that it's the first page that is causing the callback to fire after the chat window is closed: -first-paste doesn't paste right away, but if i leave the chat window open long enough, it does eventually show up -if i close the chat window before it shows up, i get the crash (pre-patch). if i leave the chat window open until the paste shows up, i can close it later, and get no crash.
Merged; will be in 2.30.1 This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.