deluge crashed with SIGSEGV when removing torrents

Bug #1049332 reported by Juan M. Hidalgo
150
This bug affects 23 people
Affects Status Importance Assigned to Milestone
Deluge
Fix Released
Unknown
libtorrent-rasterbar
Unknown
Unknown
deluge (Debian)
Fix Released
Unknown
deluge (Ubuntu)
Fix Released
Medium
Andrew Starr-Bochicchio
libtorrent-rasterbar (Ubuntu)
Invalid
Medium
Andrew Starr-Bochicchio

Bug Description

Crashed trying to remove torrents

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: deluge-gtk 1.3.5-1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Tue Sep 11 10:59:18 2012
ExecutablePath: /usr/bin/deluge-gtk
InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/deluge-gtk
ProcEnviron:
 LANGUAGE=es_ES:en
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x48aaf8: addl $0x1,0x98(%r13)
 PC (0x0048aaf8) 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-10 (1 days ago)
UserGroups: adm admin cdrom debian-tor dialout fuse libvirtd lp lpadmin netdev plugdev sambashare vboxusers

Related branches

Revision history for this message
Juan M. Hidalgo (juanmhidalgo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 subtype_dealloc.25740 (self=<torrent_plugin at remote 0x266bcf8>) at ../Objects/typeobject.c:951
 ?? ()
 ?? ()
 release (this=0x7f265c0c5130) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:145
 ~shared_count (this=0x7f265c0c5160, __in_chrg=<optimized out>) at /usr/include/boost/smart_ptr/detail/shared_count.hpp:305

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in deluge (Ubuntu):
importance: Undecided → Medium
summary: - deluge-gtk crashed with SIGSEGV in
- boost::python::converter::shared_ptr_deleter::operator()
+ deluge-gtk crashed with SIGSEGV in subtype_dealloc.25740()
tags: removed: need-amd64-retrace
Cas (calumlind)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: deluge-gtk crashed with SIGSEGV in subtype_dealloc.25740()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in deluge (Ubuntu):
status: New → Confirmed
Revision history for this message
Cas (calumlind) wrote :

This is a problem with libtorrent 0.16 and needs reporting upstream: https://code.google.com/p/libtorrent/issues/list

The solution for now is to install libtorrent 0.15.

summary: - deluge-gtk crashed with SIGSEGV in subtype_dealloc.25740()
+ deluge crashed with SIGSEGV when removing torrents
Revision history for this message
Jared Greenwald (jetsaredim) wrote :

I don't think the 0.15 version is available in the quantal repos...

Changed in deluge:
status: Unknown → New
Changed in libtorrent-rasterbar (Ubuntu):
status: New → Confirmed
Changed in libtorrent-rasterbar (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Aurimas Fišeras (aurimas-gmail) wrote :

Are you sure it's a problem in libtorrent-rasterbar 0.16?
I've rebuilt libtorrent-rasterbar 0.15.10-1ubuntu1 from precise in quantal, but still get crashes when removing a torrent.
Maybe it's a problem with libboost (or libboost + libtorrent), since libboost version changed in quantal?

Revision history for this message
Cas (calumlind) wrote :

There is a fix applied to the RC 0.16 branch of libtorrent and from my limited testing of it, it fixes the issue.

http://libtorrent.svn.sourceforge.net/viewvc/libtorrent/branches/RC_0_16/

Cas (calumlind)
Changed in deluge (Ubuntu):
status: Confirmed → Invalid
Changed in libtorrent-rasterbar (Ubuntu):
status: Confirmed → Fix Committed
Changed in libtorrent-rasterbar (Ubuntu):
status: Fix Committed → In Progress
assignee: nobody → Andrew Starr-Bochicchio (andrewsomething)
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

My comment from the upstream bug, re: the svn snapshot:

"In my testing, this seems to cause some sort of regression with magnet links. I've tested with both an svn snapshot of the current state of the RC_0_16 branch as well as 0.16.3 with just rev 7422 applied as a patch. In both cases, when a magnet link is added it seems to find peers but never actually download any files, not even the file list. Using torrent files, things work as expected.

Interestingly, if I add a magnet link with 0.16.3, shutdown deluge, install the patched version, and restart deluge, it continues to download. So it seems that there is just something wrong with getting that first bit of information.

Deluge never shows any python tracebacks, and there is never a crash in libtorrent."

Revision history for this message
Chad Miller (cmiller) wrote :

I can't reproduce that magnet-link regression reported in #13.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "debdiff to 0.16rc. changelog needs work." of this bug report has been identified as being a patch in the form of a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
tags: added: running-unity
Revision history for this message
Cas (calumlind) wrote :

The debdiff is not correct as the package diff should be against libtorrent-rasterbar not libtorrent.

Revision history for this message
Cas (calumlind) wrote :

Please see my updated comment and patch for fixing the issue in Deluge without the need for libtorrent fix.

http://dev.deluge-torrent.org/ticket/2160#comment:9

Changed in deluge (Ubuntu):
status: Invalid → Triaged
status: Triaged → Confirmed
Changed in deluge (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Andrew Starr-Bochicchio (andrewsomething)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package deluge - 1.3.5-1ubuntu3

---------------
deluge (1.3.5-1ubuntu3) quantal; urgency=low

  * debian/patches/lt_gil_fix.patch:
   - Disable add_extenstion and use session flags instead for
     libtorrent extensions (LP: #1049332).
 -- Andrew Starr-Bochicchio <email address hidden> Wed, 26 Sep 2012 10:07:13 -0400

Changed in deluge (Ubuntu):
status: In Progress → Fix Released
Changed in libtorrent-rasterbar (Ubuntu):
status: In Progress → Invalid
Changed in deluge:
status: New → Fix Released
Changed in deluge (Debian):
status: Unknown → New
Changed in deluge (Debian):
status: New → Fix Released
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.