pidgin crashed with SIGSEGV in g_slice_free_chain_with_offset()

Bug #206523 reported by Garfield
6
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: pidgin

Im not sure what's going on...

ProblemType: Crash
Architecture: amd64
Date: Tue Mar 25 21:20:46 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.3.1-2ubuntu1
PackageArchitecture: amd64
ProcCmdline: pidgin
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_slice_free_chain_with_offset ()
 pango_attr_list_unref ()
Title: pidgin crashed with SIGSEGV in g_slice_free_chain_with_offset()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev vboxusers video
SegvAnalysis:
 Segfault happened at: 0x7f7f698a5ae8: mov %rax,0x18(%rcx)
 PC (0x7f7f698a5ae8) ok
 source "%rax" ok
 destination "0x18(%rcx)" (0x00000018) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA

Tags: apport-crash
Revision history for this message
Garfield (kiddyfurby) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:magazine_cache_push_magazine (ix=<value optimized out>,
thread_memory_magazine2_unload (tmem=<value optimized out>,
IA__g_slice_free_chain_with_offset (mem_size=16,
pango_attr_list_unref (list=0x1884460)
pango_layout_finalize (object=0x1462bd0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in pidgin:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

Changed in pidgin:
status: New → Incomplete
Revision history for this message
Garfield (kiddyfurby) wrote : Re: [Bug 206523] Re: pidgin crashed with SIGSEGV in g_slice_free_chain_with_offset()

I still have a 3-4 crash everyday in Intrepid. I will see if I can reproduce
the same bug.

On Jan 6, 2009 3:47 AM, "Pedro Villavicencio" <email address hidden> wrote:

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04?
Thanks in advance.

** Changed in: pidgin (Ubuntu)
      Status: New => Incomplete

--
pidgin crashed with SIGSEGV in g_slice_free_chain_with_offset()
https://bugs.launchpad.net/bugs/206523
You received this bug notification because you are a direct subscriber
of the bug.

Revision history for this message
Garfield (kiddyfurby) wrote :

I've yet to capture a crash in Intrepid, I played around with other distro for a period, and is switching to Jaunty
I think this is not a Intrepid specific bug, as pidgin always quit unexpectedly.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Revision history for this message
Garfield (kiddyfurby) wrote :

I m unable to reproduce the problem by myself
It just happen randomly, so I simply started pidgin and let it run...
Pidgin eventually crashed after a few hours, but the log file is almost 30Mb

visibility: private → public
Kees Cook (kees)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in pidgin (Ubuntu):
status: Incomplete → Expired
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.