deluge-gtk assert failure: *** glibc detected *** /usr/bin/python: double free or corruption (!prev): 0x0ab99280 ***

Bug #872644 reported by Fabio Duran Verdugo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
deluge (Ubuntu)
New
Undecided
Unassigned

Bug Description

minimize deluge cause crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: deluge-gtk 1.3.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/python: double free or corruption (!prev): 0x0ab99280 ***
CrashCounter: 1
Date: Wed Oct 12 00:21:32 2011
ExecutablePath: /usr/bin/deluge-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/deluge-gtk /home/username/Downloads/torrent.cd.707a93b30569ca0908cd32d5716ddf29365b6650.torrent
Signal: 6
SourcePackage: deluge
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x27c080 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0xab99280) at malloc.c:6283
 _int_free (av=0x2b8400, p=0xab99278) at malloc.c:4795
 __GI___libc_free (mem=0xab99280) at malloc.c:3738
 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
Title: deluge-gtk assert failure: *** glibc detected *** /usr/bin/python: double free or corruption (!prev): 0x0ab99280 ***
UpgradeStatus: Upgraded to oneiric on 2011-07-31 (72 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers

Revision history for this message
Fabio Duran Verdugo (fabioduran) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #871454, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.