empathy-chat crashed with SIGSEGV in _tpl_event_queue_insert_sorted_after()

Bug #915047 reported by Cristian Aravena Romero
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Empathy
Invalid
High
empathy (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Work with empathy, account Gtalk, MSN, chat, Facebook and salut... ON. Click in user gtalk and crash.

Duplicated bug #807566 (?)

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: empathy 3.2.0.1-0ubuntu1.1
Uname: Linux 3.1.8-030108-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Jan 11 18:28:36 2012
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: /usr/lib/empathy/empathy-chat
SegvAnalysis:
 Segfault happened at: 0x7f867b532d6e <_tpl_event_queue_insert_sorted_after+78>: mov (%rdx),%rdi
 PC (0x7f867b532d6e) ok
 source "(%rdx)" (0x39373a746168632d) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 _tpl_event_queue_insert_sorted_after (events=0x7f865de0dad0, index=0x7f8664026700, event=0x154cf20) at util.c:128
 _tpl_log_manager_get_filtered_events (manager=<optimized out>, account=0x1528630, target=0x14d6300, type_mask=1, num_events=5, filter=0x43ebb0 <chat_log_filter>, user_data=0x1570080) at log-manager.c:592
 _get_filtered_events_async_thread (simple=0x1cc2700, object=<optimized out>, cancellable=<optimized out>) at log-manager.c:1086
 run_in_thread (job=<optimized out>, c=0x0, _data=0x15b7190) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:843
 io_job_thread (data=0x1de3080, user_data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gio/gioscheduler.c:180
Title: empathy-chat crashed with SIGSEGV in _tpl_event_queue_insert_sorted_after()
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (99 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
In , Guillaume-desmottes (guillaume-desmottes) wrote :

Original bug report: https://bugzilla.gnome.org/show_bug.cgi?id=661282

#0 0x00007fbe27d51d6e in _tpl_event_queue_insert_sorted_after (events=0x7fbdc672dad0, index=0x7fbe100a1960, event=0x1ed55d0) at util.c:128
#1 0x00007fbe27d4437d in _tpl_log_manager_get_filtered_events (manager=<optimized out>, account=0x15f9630, target=0x1ecc300, type_mask=1,
    num_events=5, filter=0x43ebb0 <chat_log_filter>, user_data=0x164a490) at log-manager.c:592
#2 0x00007fbe27d44416 in _get_filtered_events_async_thread (simple=0x1681f00, object=<optimized out>, cancellable=<optimized out>)
    at log-manager.c:1086
#3 0x00007fbe23ebfafc in run_in_thread (job=<optimized out>, c=0x0, _data=0x1f763e0)
    at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:843
#4 0x00007fbe23eb13f6 in io_job_thread (data=0x1c9f890, user_data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gio/gioscheduler.c:180
#5 0x00007fbe237787d8 in g_thread_pool_thread_proxy (data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gthreadpool.c:319
#6 0x00007fbe237762b6 in g_thread_create_proxy (data=0x1c989e0) at /build/buildd/glib2.0-2.30.0/./glib/gthread.c:1962
#7 0x00007fbe241a1efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#8 0x00007fbe2309c89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#9 0x0000000000000000 in ?? ()

See https://bugzilla.gnome.org/page.cgi?id=trace.html&trace_id=228773 for the full trace

Revision history for this message
In , Nicolas-dufresne (nicolas-dufresne) wrote :

There is nothing helpful in this trace, I would need information about the local variables or step to reproduce.

Revision history for this message
In , Nicolas-dufresne (nicolas-dufresne) wrote :

After 300 clicks going over all of my contacts I still can't reproduce this crash.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _tpl_event_queue_insert_sorted_after (events=0x7f865de0dad0, index=0x7f8664026700, event=0x154cf20) at util.c:128
 _tpl_log_manager_get_filtered_events (manager=<optimized out>, account=0x1528630, target=0x14d6300, type_mask=1, num_events=5, filter=0x43ebb0 <chat_log_filter>, user_data=0x1570080) at log-manager.c:592
 _get_filtered_events_async_thread (simple=0x1cc2700, object=<optimized out>, cancellable=<optimized out>) at log-manager.c:1086
 run_in_thread (job=<optimized out>, c=0x0, _data=0x15b7190) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:843
 io_job_thread (data=0x1de3080, user_data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gio/gioscheduler.c:180

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in empathy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in empathy:
importance: Unknown → Critical
Revision history for this message
In , Guillaume-desmottes (guillaume-desmottes) wrote :

Someone else experienced this crash: https://bugzilla.gnome.org/show_bug.cgi?id=666684

Revision history for this message
Bilal Shahid (s9iper1) wrote :

have you facing this crash with empathy 3.3.4 ?

Changed in empathy (Ubuntu):
status: New → Incomplete
Changed in empathy:
importance: Critical → Unknown
Changed in empathy:
importance: Unknown → High
status: Unknown → Invalid
Bilal Shahid (s9iper1)
Changed in empathy (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
In , Guillaume-desmottes (guillaume-desmottes) wrote :

This bug is in the top 5 of the most common empathy crash on Ubuntu ( https://errors.ubuntu.com/?package=empathy ) so I think we may have to re-open.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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