deluge-gtk crashed with SIGSEGV in std::_Rb_tree_rebalance_for_erase()

Bug #1208213 reported by madigor on 2013-08-04
This bug affects 2 people
Affects Status Importance Assigned to Milestone
deluge (Ubuntu)
libtorrent-rasterbar (Ubuntu)

Bug Description


ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: deluge-gtk 1.3.6-0ubuntu2
Uname: Linux 3.10.1-031001-generic x86_64
ApportVersion: 2.12-0ubuntu2
Architecture: amd64
Date: Sun Aug 4 07:09:51 2013
ExecutablePath: /usr/bin/deluge-gtk
InstallationDate: Installed on 2012-08-01 (367 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/deluge-gtk
 PATH=(custom, no user)
 Segfault happened at: 0x7f3d2051f0c4 <_ZSt28_Rb_tree_rebalance_for_erasePSt18_Rb_tree_node_baseRS_+388>: mov (%rdi),%r9d
 PC (0x7f3d2051f0c4) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r9d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: deluge
 std::_Rb_tree_rebalance_for_erase(std::_Rb_tree_node_base*, std::_Rb_tree_node_base&) () from /usr/lib/x86_64-linux-gnu/
 libtorrent::udp_tracker_connection::start_announce() () from /usr/lib/
 libtorrent::udp_tracker_connection::name_lookup(boost::system::error_code const&, boost::asio::ip::basic_resolver_iterator<boost::asio::ip::tcp>) () from /usr/lib/
 ?? () from /usr/lib/
 boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) () from /usr/lib/
Title: deluge-gtk crashed with SIGSEGV in std::_Rb_tree_rebalance_for_erase()
UpgradeStatus: Upgraded to saucy on 2013-07-19 (16 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

madigor (madigor) wrote :

 std::_Rb_tree_rebalance_for_erase(std::_Rb_tree_node_base*, std::_Rb_tree_node_base&) () from /tmp/apport_sandbox_bcHxR6/usr/lib/x86_64-linux-gnu/
 _M_erase_aux (__position=..., this=0x7f3d20f296e0 <libtorrent::udp_tracker_connection::m_connection_cache>) at /usr/include/c++/4.8/bits/stl_tree.h:1745
 erase (__position=..., this=0x7f3d20f296e0 <libtorrent::udp_tracker_connection::m_connection_cache>) at /usr/include/c++/4.8/bits/stl_tree.h:826
 erase (__position=..., this=0x7f3d20f296e0 <libtorrent::udp_tracker_connection::m_connection_cache>) at /usr/include/c++/4.8/bits/stl_map.h:711
 libtorrent::udp_tracker_connection::start_announce (this=this@entry=0x7f3d100df660) at ../../src/udp_tracker_connection.cpp:290

Changed in deluge (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Cas (calumlind) wrote :

This potentially could be fixed in later version of libtorrent 0.16, there is a PPA that contains up to date versions here:

Changed in deluge (Ubuntu):
status: New → Invalid
information type: Private → Public
tags: added: xenial
Launchpad Janitor (janitor) wrote :

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

Changed in libtorrent-rasterbar (Ubuntu):
status: New → Confirmed
Cas (calumlind) wrote :
Changed in libtorrent-rasterbar (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers