self terminating bug #920

Closed
opened 2026-02-21 15:23:00 -05:00 by deekerman · 8 comments
Owner

Originally created by @hathalud on GitHub (Nov 14, 2013).

The following is the error that I get running qbittorrent-nox for about 2 minutes on openmediavault v4.35 (a Debian Squeeze distro)


Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
/lib/libc.so.6 : ()+0x32230 [0x7f78e102c230]
/usr/lib/libcrypto.so.0.9.8 : RC4()+0x3f4 [0x7f78e046b9a4]
/usr/lib/libtorrent-rasterbar.so.5 : ()+0x27da86 [0x7f78e2767a86]
/usr/lib/libtorrent-rasterbar.so.5 : ()+0x27e26c [0x7f78e276826c]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_extended(int)+0xeb [0x7f78e262f90b]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::dispatch_message(int)+0x14a [0x7f78e263004a]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_receive(boost::system::error_code const&, unsigned long)+0x252 [0x7f78e2630892]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::peer_connection::on_receive_data(boost::system::error_code const&, unsigned long)+0x112 [0x7f78e260cec2]
/usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::handler_queue::handler_wrapper<boost::asio::detail::binder2<boost::_bi::bind_t<void, boost::_mfi::mf2<void, libtorrent::peer_connection, boost::system::error_code const&, unsigned long>, boost::_bi::list3boost::_bi::value<boost::intrusive_ptr<libtorrent::peer_connection >, boost::arg<1>, boost::arg<2> > >, boost::system::error_code, unsigned long> >::do_call(boost::asio::detail::handler_queue::handler*)+0xe8 [0x7f78e2611c98]
/usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::task_io_serviceboost::asio::detail::epoll_reactor::run(boost::system::error_code&)+0x346 [0x7f78e2620906]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::aux::session_impl::operator()()+0x71 [0x7f78e2666081]
/usr/lib/libboost_thread.so.1.42.0 : thread_proxy()+0x60 [0x7f78e09d4200]
/lib/libpthread.so.0 : ()+0x68ca [0x7f78e22d48ca]
/lib/libc.so.6 : clone()+0x6d [0x7f78e10c9b6d]

Originally created by @hathalud on GitHub (Nov 14, 2013). The following is the error that I get running qbittorrent-nox for about 2 minutes on openmediavault v4.35 (a Debian Squeeze distro) --- Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: stack trace: /lib/libc.so.6 : ()+0x32230 [0x7f78e102c230] /usr/lib/libcrypto.so.0.9.8 : RC4()+0x3f4 [0x7f78e046b9a4] /usr/lib/libtorrent-rasterbar.so.5 : ()+0x27da86 [0x7f78e2767a86] /usr/lib/libtorrent-rasterbar.so.5 : ()+0x27e26c [0x7f78e276826c] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_extended(int)+0xeb [0x7f78e262f90b] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::dispatch_message(int)+0x14a [0x7f78e263004a] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_receive(boost::system::error_code const&, unsigned long)+0x252 [0x7f78e2630892] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::peer_connection::on_receive_data(boost::system::error_code const&, unsigned long)+0x112 [0x7f78e260cec2] /usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::handler_queue::handler_wrapper<boost::asio::detail::binder2<boost::_bi::bind_t<void, boost::_mfi::mf2<void, libtorrent::peer_connection, boost::system::error_code const&, unsigned long>, boost::_bi::list3boost::_bi::value<boost::intrusive_ptr<libtorrent::peer_connection >, boost::arg<1>, boost::arg<2> > >, boost::system::error_code, unsigned long> >::do_call(boost::asio::detail::handler_queue::handler*)+0xe8 [0x7f78e2611c98] /usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::task_io_serviceboost::asio::detail::epoll_reactor<false >::run(boost::system::error_code&)+0x346 [0x7f78e2620906] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::aux::session_impl::operator()()+0x71 [0x7f78e2666081] /usr/lib/libboost_thread.so.1.42.0 : thread_proxy()+0x60 [0x7f78e09d4200] /lib/libpthread.so.0 : ()+0x68ca [0x7f78e22d48ca] /lib/libc.so.6 : clone()+0x6d [0x7f78e10c9b6d]
deekerman 2026-02-21 15:23:00 -05:00
  • closed this issue
  • added the
    Crash
    label
Author
Owner

@hathalud commented on GitHub (Nov 14, 2013):

Seems to be a bug related to the que. I started with three torrents allowed at a time and it crashed. Dropped it to one and it worked fine. Bumped it up to two concurrent torrents and it crashed almost immediately again. So I currently have it running with just one torrent. It's not ideal, but it works for the moment. And QBittorrent is the only torrent app that meets my needs.

@hathalud commented on GitHub (Nov 14, 2013): Seems to be a bug related to the que. I started with three torrents allowed at a time and it crashed. Dropped it to one and it worked fine. Bumped it up to two concurrent torrents and it crashed almost immediately again. So I currently have it running with just one torrent. It's not ideal, but it works for the moment. And QBittorrent is the only torrent app that meets my needs.
Author
Owner

@hathalud commented on GitHub (Nov 14, 2013):

it crashed later after finishing that first torrent.


Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
/lib/libc.so.6 : ()+0x32230 [0x7fcef0627230]
/usr/lib/libcrypto.so.0.9.8 : RC4()+0x3f4 [0x7fceefa669a4]
/usr/lib/libtorrent-rasterbar.so.5 : ()+0x27da86 [0x7fcef1d62a86]
/usr/lib/libtorrent-rasterbar.so.5 : ()+0x27e26c [0x7fcef1d6326c]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_extended(int)+0xeb [0x7fcef1c2a90b]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::dispatch_message(int)+0x14a [0x7fcef1c2b04a]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_receive(boost::system::error_code const&, unsigned long)+0x252 [0x7fcef1c2b892]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::peer_connection::on_receive_data(boost::system::error_code const&, unsigned long)+0x112 [0x7fcef1c07ec2]
/usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::handler_queue::handler_wrapper<boost::asio::detail::binder2<boost::_bi::bind_t<void, boost::_mfi::mf2<void, libtorrent::peer_connection, boost::system::error_code const&, unsigned long>, boost::_bi::list3boost::_bi::value<boost::intrusive_ptr<libtorrent::peer_connection >, boost::arg<1>, boost::arg<2> > >, boost::system::error_code, unsigned long> >::do_call(boost::asio::detail::handler_queue::handler*)+0xe8 [0x7fcef1c0cc98]
/usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::task_io_serviceboost::asio::detail::epoll_reactor::run(boost::system::error_code&)+0x346 [0x7fcef1c1b906]
/usr/lib/libtorrent-rasterbar.so.5 : libtorrent::aux::session_impl::operator()()+0x71 [0x7fcef1c61081]
/usr/lib/libboost_thread.so.1.42.0 : thread_proxy()+0x60 [0x7fceeffcf200]
/lib/libpthread.so.0 : ()+0x68ca [0x7fcef18cf8ca]
/lib/libc.so.6 : clone()+0x6d [0x7fcef06c4b6d]

@hathalud commented on GitHub (Nov 14, 2013): it crashed later after finishing that first torrent. --- Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: stack trace: /lib/libc.so.6 : ()+0x32230 [0x7fcef0627230] /usr/lib/libcrypto.so.0.9.8 : RC4()+0x3f4 [0x7fceefa669a4] /usr/lib/libtorrent-rasterbar.so.5 : ()+0x27da86 [0x7fcef1d62a86] /usr/lib/libtorrent-rasterbar.so.5 : ()+0x27e26c [0x7fcef1d6326c] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_extended(int)+0xeb [0x7fcef1c2a90b] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::dispatch_message(int)+0x14a [0x7fcef1c2b04a] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::bt_peer_connection::on_receive(boost::system::error_code const&, unsigned long)+0x252 [0x7fcef1c2b892] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::peer_connection::on_receive_data(boost::system::error_code const&, unsigned long)+0x112 [0x7fcef1c07ec2] /usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::handler_queue::handler_wrapper<boost::asio::detail::binder2<boost::_bi::bind_t<void, boost::_mfi::mf2<void, libtorrent::peer_connection, boost::system::error_code const&, unsigned long>, boost::_bi::list3boost::_bi::value<boost::intrusive_ptr<libtorrent::peer_connection >, boost::arg<1>, boost::arg<2> > >, boost::system::error_code, unsigned long> >::do_call(boost::asio::detail::handler_queue::handler*)+0xe8 [0x7fcef1c0cc98] /usr/lib/libtorrent-rasterbar.so.5 : boost::asio::detail::task_io_serviceboost::asio::detail::epoll_reactor<false >::run(boost::system::error_code&)+0x346 [0x7fcef1c1b906] /usr/lib/libtorrent-rasterbar.so.5 : libtorrent::aux::session_impl::operator()()+0x71 [0x7fcef1c61081] /usr/lib/libboost_thread.so.1.42.0 : thread_proxy()+0x60 [0x7fceeffcf200] /lib/libpthread.so.0 : ()+0x68ca [0x7fcef18cf8ca] /lib/libc.so.6 : clone()+0x6d [0x7fcef06c4b6d]
Author
Owner

@sledgehammer999 commented on GitHub (Nov 16, 2013):

This is a known problem with 0.15.x. It is a fault of libtorrent. See #750 and http://qbforums.shiki.hu/index.php/topic,2197.msg7992.html#msg7992

@sledgehammer999 commented on GitHub (Nov 16, 2013): This is a known problem with 0.15.x. It is a fault of libtorrent. See #750 and http://qbforums.shiki.hu/index.php/topic,2197.msg7992.html#msg7992
Author
Owner

@hathalud commented on GitHub (Nov 16, 2013):

So if I understand this correctly, by disabling the encryption in qbittorrent everything should work fine? That'd be great if it's a simple work around like that.... I've been limping along with a pair of cron jobs that check every minute to see if qbittorrent is running and needs to be started... and then restart it hourly incase that fails (which happens for some reason). If just disabling the encryption works, I can ditch those two cron jobs.

@hathalud commented on GitHub (Nov 16, 2013): So if I understand this correctly, by disabling the encryption in qbittorrent everything should work fine? That'd be great if it's a simple work around like that.... I've been limping along with a pair of cron jobs that check every minute to see if qbittorrent is running and needs to be started... and then restart it hourly incase that fails (which happens for some reason). If just disabling the encryption works, I can ditch those two cron jobs.
Author
Owner

@hathalud commented on GitHub (Nov 16, 2013):

Even with that change it still seems to be terminating unexpectedly.

@hathalud commented on GitHub (Nov 16, 2013): Even with that change it still seems to be terminating unexpectedly.
Author
Owner

@sledgehammer999 commented on GitHub (Nov 17, 2013):

Does it have the same backtrace? If yes, then probably you'll have to update libtorrent.

@sledgehammer999 commented on GitHub (Nov 17, 2013): Does it have the same backtrace? If yes, then probably you'll have to update libtorrent.
Author
Owner

@hathalud commented on GitHub (Nov 17, 2013):

Looks like one of the scripts I was using was causing the deamon to crash. Thanks for all the help!

@hathalud commented on GitHub (Nov 17, 2013): Looks like one of the scripts I was using was causing the deamon to crash. Thanks for all the help!
Author
Owner

@sledgehammer999 commented on GitHub (Nov 17, 2013):

No problem. If you are up to it you can grab the libtorrent+qbittorrent debian source packages from sid and build locally. It will produce .debs for you.

@sledgehammer999 commented on GitHub (Nov 17, 2013): No problem. If you are up to it you can grab the libtorrent+qbittorrent **debian** source packages from sid and build locally. It will produce .debs for you.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#920
No description provided.