[apport] gaim crashed with SIGSEGV in pthread_mutex_lock()

Bug #86930 reported by Michael R. Head
2
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gaim

I'm not super excited about reporting this bug, but maybe it can be retargetted and resummarized if there's something useful in these apport files.

Basically what happened was that I left my machine in the morning with gaim on and came back at night. When I attempted to access gaim, I was able to read some of the messages that had collected during the day but at some point, gaim locked up. All the windows repainted with the flat gray color that indicates the program's GTK main loop is hung. Hoping there was something I could do besides killall gaim, I did a "sudo invoke-rc.d dbus restart". It was during the dbus restart process that gaim crashed and produced this report.

If this is useless, feel free to close, and I apologize for wasting malone resources. Next time it happens, I'll try to attach to the process via gdb and get a better stack trace.

ProblemType: Crash
CrashCounter: 1
Date: Wed Feb 21 23:16:32 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gaim
Package: gaim 1:2.0.0+beta6-1ubuntu1
ProcCmdline: gaim
ProcCwd: /home/burner
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gaim
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 pthread_mutex_lock ()
 malloc () from /lib/tls/i686/cmov/libc.so.6
 IA__g_malloc (n_bytes=16) at gmem.c:131
 ORBit_alloc_simple () from /usr/lib/libORBit-2.so.0
Uname: Linux phoenix 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Michael R. Head (burner) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)

Changed in gaim:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Michael R. Head (burner) wrote :

I will try. I'll run it that way, leave it up for the day and hope that it happens again.

Revision history for this message
Michael R. Head (burner) wrote :

I'll close this for now, because I haven't been able to reproduce. I'll reopen if I see it again.

Changed in gaim:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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