deluge-gtk crashed with SIGSEGV in boost::python::converter::shared_ptr_deleter::operator()

[Ian Garcez Rossiter]

removing torrent without data

Description: Ubuntu quantal (development branch)
Release: 12.10

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: deluge-gtk 1.3.5-1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.20-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 18 10:24:18 2012
ExecutablePath: /usr/bin/deluge-gtk
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/deluge-gtk
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x48a5a8: addl $0x1,0x98(%r13)
 PC (0x0048a5a8) ok
 source "$0x1" ok
 destination "0x98(%r13)" (0x00000098) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: deluge
StacktraceTop:
 ?? ()
 boost::python::converter::shared_ptr_deleter::operator()(void const*) () from /usr/lib/libboost_python-py27.so.1.49.0
 std::_List_base<boost::shared_ptr<libtorrent::torrent_plugin>, std::allocator<boost::shared_ptr<libtorrent::torrent_plugin> > >::_M_clear() () from /usr/lib/libtorrent-rasterbar.so.6
 libtorrent::torrent::~torrent() () from /usr/lib/libtorrent-rasterbar.so.6
 libtorrent::torrent::~torrent() () from /usr/lib/libtorrent-rasterbar.so.6
Title: deluge-gtk crashed with SIGSEGV in boost::python::converter::shared_ptr_deleter::operator()
UpgradeStatus: Upgraded to quantal on 2012-09-11 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1049332, 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.