telepathy-idle assert failure: *** glibc detected *** /usr/lib/telepathy/telepathy-idle: free(): invalid pointer: 0x090db480 ***

Bug #546246 reported by John Pugh
38
This bug affects 4 people
Affects Status Importance Assigned to Milestone
telepathy-idle
Fix Released
High
telepathy-idle (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: telepathy-idle

crash occured just after a URL was sent directly

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/lib/telepathy/telepathy-idle: free(): invalid pointer: 0x090db480 ***
Date: Wed Mar 24 14:04:49 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/telepathy/telepathy-idle
NonfreeKernelModules: nvidia
Package: telepathy-idle 0.1.6-1
ProcCmdline: /usr/lib/telepathy/telepathy-idle
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Signal: 6
SourcePackage: telepathy-idle
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: telepathy-idle assert failure: *** glibc detected *** /usr/lib/telepathy/telepathy-idle: free(): invalid pointer: 0x090db480 ***
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
John Pugh (jpugh) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 __libc_message (do_abort=2,
 malloc_printerr (action=<value optimized out>,

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 telepathy-idle (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Thanks for the report. I've made the bug public, but I have to let you know there's a part of conversation with vorlon in the stacktrace (just once sentence, nothing really personal!).

I can confirm this bug occurs quite often in version 0.1.6-1, causing a reconnection to IRC.

visibility: private → public
Changed in telepathy-idle (Ubuntu):
importance: Medium → High
status: New → Triaged
Revision history for this message
Omer Akram (om26er) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in telepathy-idle (Ubuntu):
importance: High → Medium
status: Triaged → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

actually you could use this method for already running programs to get the logs.

https://wiki.ubuntu.com/Backtrace#Already running programs

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Omer: the Apport trace is already present and very rich. Somebody should just report this upstream.

Changed in telepathy-idle (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Omer Akram (om26er) wrote :

these logs dont have anything useful. if its still an issue please get a backtrace and send the bug upstream

Revision history for this message
John Pugh (jpugh) wrote :

I get so many crashes in empathy it is largely unusable. If others would like to backtrace it, please do. I've moved on.

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

#7 0x00b03086 in g_realloc_n () from /lib/libglib-2.0.so.0
No symbol table info available.
#8 0x00224e45 in tp_debug_sender_constructor (type=151893216,
    n_construct_params=3215588520, construct_params=0x3736b6)
    at debug-sender.c:207
 retval = <value optimized out>
#9 0x00224f76 in tp_debug_sender_set_property (object=0x90bc030,
    property_id=3215588408, value=0x90c7ca8, pspec=0x80) at debug-sender.c:175

Looks like this could enough for the developers: it seems that the crash comes from a call to g_realloc_n() at debug-sender.c:207. What other information do you expect? Of course, the crash could come from memory corruption elsewhere, and which is only unveiled while constructing this GObject, but, well, another trace won't help AFAICS.

Revision history for this message
In , Milan Bouchet-Valat (nalimilan) wrote :
Download full text (6.5 KiB)

This crash is occurring regularly while using IRC with Empathy on Ubuntu 10.04. telepathy-idle is version 0.1.6-1, telepathy 0.10.1-1ubuntu2. Several users are experiencing it, see https://bugs.launchpad.net/ubuntu/+source/telepathy-idle/+bug/546246

I hope the trace is good enough, and the crash isn't already fixed!

#0 0x007e1422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x00314641 in *__GI_raise (sig=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 resultvar = <value optimized out>
 pid = 4456436
 selftid = 3103
#2 0x00317a72 in *__GI_abort () at abort.c:92
 act = {__sigaction_handler = {
    sa_handler = 0xa124e4 <_rtld_local+1220>,
    sa_sigaction = 0xa124e4 <_rtld_local+1220>}, sa_mask = {__val = {917504,
      134583744, 134520168, 3215586392, 7175, 3215586360, 134515384,
      134515324, 3, 10561784, 3865137, 3, 134583744, 3215586288, 4456436, 25,
      3215587748, 3215586408, 3984180, 2, 3215586288, 4, 0, 3215586384,
      3215586396, 2, 4312327, 4312323, 4307873, 4307899, 230, 3215586288}},
  sa_flags = -1079380936, sa_restorer = 0x41e0a3}
 sigs = {__val = {32, 0 <repeats 31 times>}}
#3 0x0034b48d in __libc_message (do_abort=2,
    fmt=0x41fef8 "*** glibc detected *** %s: %s: 0x%s ***\n")
    at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 ap = <value optimized out>
 fd = -1079380576
 on_2 = <value optimized out>
 list = <value optimized out>
 nlist = <value optimized out>
 cp = <value optimized out>
 written = false
#4 0x00355581 in malloc_printerr (action=<value optimized out>,
    str=0x6 <Address 0x6 out of bounds>, ptr=0x90db480) at malloc.c:6264
 buf = "090db480"
 cp = <value optimized out>
#5 0x00356dd8 in _int_free (av=<value optimized out>,
    p=<value optimized out>) at malloc.c:4792
 size = 0
 nextchunk = (mchunkptr) 0xc1f
 nextsize = 12093416
 prevsize = <value optimized out>
 bck = <value optimized out>
 fwd = <value optimized out>
 errstr = 0x6 <Address 0x6 out of bounds>
 __func__ = "_int_free"
#6 0x00359ebd in *__GI___libc_free (mem=0x90db480) at malloc.c:3738
 ar_ptr = (mstate) 0x4413c0
 p = (mchunkptr) 0x6
#7 0x00b03086 in g_realloc_n () from /lib/libglib-2.0.so.0
No symbol table info available.
#8 0x00224e45 in tp_debug_sender_constructor (type=151893216,
    n_construct_params=3215588520, construct_params=0x3736b6)
    at debug-sender.c:207
 retval = <value optimized out>
#9 0x00224f76 in tp_debug_sender_set_property (object=0x90bc030,
    property_id=3215588408, value=0x90c7ca8, pspec=0x80) at debug-sender.c:175
No locals.
#10 0x0804decd in idle_debug (flag=IDLE_DEBUG_PARSER,
    format=0x8063123 "%s: set handle %u") at idle-debug.c:97
 message = (gchar *) 0x9109920 "_parse_atom: set handle 63"
#11 0x0805502e in _parse_atom (parser=<value optimized out>,
    arr=<value optimized out>, atom=99 'c', token=<value optimized out>,
    contact_reffed=0x911dc28, room_reffed=0x90f06c8) at idle-parser.c:493
 id = <value optimized out>
 modechar = 0 '\0'
 priv = (IdleParserPrivate *) 0x90cc028
 handle = 6
 val = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0,
      v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0,
      v_pointer = 0x0}, {v_int = ...

Read more...

Changed in telepathy-idle:
importance: Unknown → High
status: Unknown → Confirmed
Revision history for this message
In , Will Thompson (wjt) wrote :

This backtrace doesn't make much sense: for instance, the frame above main() is tp_text_mixin_get_message_types(), which cannot be the case. And skimming the code, I can't see why a debug sender would be constructed in response to an incoming message — I don't see mismatched ref/unrefs or anything.

I don't suppose you could reproduce the issue, and get an idle debug log (see <http://telepathy.freedesktop.org/wiki/Debugging>)?

Revision history for this message
In , Milan Bouchet-Valat (nalimilan) wrote :
Download full text (3.7 KiB)

I ran telepathy-idle in Valgrind with IDLE_PERSIST=1 IDLE_DEBUG=all. But I forgot to run valgrind with GSLICE=malloc, my bad! So the memory check is not interesting at all... I'll do it again, but for now here's the end of the log, if that can help:

** (telepathy-idle:5611): DEBUG: _parse_and_forward_one: message code 10
** (telepathy-idle:5611): DEBUG: _parse_atom: parsing atom "andreasma!~<email address hidden>" as c
** (telepathy-idle:5611): DEBUG: idle_nickname_is_valid: Validating nickname 'andreasma' with strict mode 0
** (telepathy-idle:5611): DEBUG: _parse_atom: set handle 252
** (telepathy-idle:5611): DEBUG: _parse_atom: parsing atom "PRIVMSG" as I
** (telepathy-idle:5611): DEBUG: _parse_atom: ignored token
** (telepathy-idle:5611): DEBUG: _parse_atom: parsing atom "#libreoffice" as r
** (telepathy-idle:5611): DEBUG: _parse_atom: set handle 3
** (telepathy-idle:5611): DEBUG: _parse_and_forward_one: set string "I get an issue with tabs inside the source code. I have only translated the comments. How can I fix the problem with the tabs?"
** (telepathy-idle:5611): DEBUG: _parse_and_forward_one: succesfully parsed
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_receive_with_flags: queued message 147
** (telepathy-idle:5611): DEBUG: _parse_and_forward_one: message code 11
** (telepathy-idle:5611): DEBUG: _parse_atom: parsing atom "andreasma!~<email address hidden>" as c
** (telepathy-idle:5611): DEBUG: idle_nickname_is_valid: Validating nickname 'andreasma' with strict mode 0
** (telepathy-idle:5611): DEBUG: _parse_atom: set handle 252
** (telepathy-idle:5611): DEBUG: _parse_atom: parsing atom "PRIVMSG" as I
** (telepathy-idle:5611): DEBUG: _parse_atom: ignored token
** (telepathy-idle:5611): DEBUG: _parse_atom: parsing atom "#libreoffice" as c
** (telepathy-idle:5611): DEBUG: idle_nickname_is_valid: Validating nickname '#libreoffice' with strict mode 0
** (telepathy-idle:5611): DEBUG: idle_nickname_is_valid: invalid character 35
** (telepathy-idle:5611): DEBUG: _parse_and_forward_one: failed to parse ":andreasma!~<email address hidden> PRIVMSG #libreoffice :I get an issue with tabs inside the source code. I have only translated the comments. How can I fix the problem with the tabs?"
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 0
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 1
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 2
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 3
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 4
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 5
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 6
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_mixin_acknowledge_pending_messages: acknowleding message id 7
(telepathy-idle:5611): tp-glib/im-DEBUG: tp_text_m...

Read more...

Changed in telepathy-idle:
importance: High → Unknown
Changed in telepathy-idle:
importance: Unknown → High
Revision history for this message
In , Milan Bouchet-Valat (nalimilan) wrote :

Doesn't seem to happen anymore in Fedora 16.

Changed in telepathy-idle:
status: Confirmed → Fix Released
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.