pidgin crashed with SIGSEGV in g_slice_free1()

Bug #130524 reported by Pavel Rojtberg
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

no additional information available

ProblemType: Crash
Architecture: i386
Date: Sun Aug 5 21:45:44 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: fglrx
Package: pidgin 1:2.1.0-1ubuntu2
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/pavel
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 g_slice_free1 () from /usr/lib/libglib-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_slice_free1()
Uname: Linux deepblue 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Pavel Rojtberg (rojtberg) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:magazine_cache_push_magazine (ix=0, magazine_chunks=<value optimized out>, count=51) at /build/buildd/glib2.0-2.13.7/glib/gslice.c:614
thread_memory_magazine2_unload (tmem=<value optimized out>, ix=0) at /build/buildd/glib2.0-2.13.7/glib/gslice.c:744
IA__g_slice_free_chain_with_offset (mem_size=8, mem_chain=0x86d24c8, next_offset=4) at /build/buildd/glib2.0-2.13.7/glib/gslice.c:928
IA__g_slist_free (slist=0x86d24c8) at /build/buildd/glib2.0-2.13.7/glib/gslist.c:53
closures_destroy (data=0x86d24c8) at /build/buildd/gtk+2.0-2.11.6/gtk/gtkwidget.c:4103

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in pidgin:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Could you try to get a valgrind log for the crash (you can follow the instructions on https://wiki.ubuntu.com/Valgrind)?

Changed in pidgin:
status: New → Incomplete
Revision history for this message
Pavel Rojtberg (rojtberg) wrote :

I will, but I could not reproduce the bug since then.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pidgin (Ubuntu) because there has been no activity for 60 days.]

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.