Open GoogleCodeExporter opened 9 years ago
Hi,
I was advised by Chris to file this report here.
https://bugzilla.redhat.com/show_bug.cgi?id=566387
Thanks
Leigh
Original comment by leigh123...@gmail.com
on 18 Feb 2010 at 2:13
The crash occurs in libtorrent::http_tracker_connection::on_response()
It was reported by several users, even with libtorrent v0.14.10
v0.14.10 is still affected by the crash in disconnect_peer() also. This bug is
very
old but still there and occurring from time to time.
Original comment by dch...@gmail.com
on 10 Apr 2010 at 1:40
[deleted comment]
I have the same bug on the Fedora 12 (architecture: x86_64)
How to reproduce:
1. open qbittorrent
2. wait ~2-3 seconds
3. qbittorrent: closed. back trace in the "Bug Description"
qbittorrent
Peer ID: -qB2490-
HTTP user agent is qBittorrent v2.4.9
*************************************************************
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
/lib64/libc.so.6() [0x3790e32870]
/usr/lib64/libtorrent-rasterbar.so.5 : libtorrent::http_tracker_connection::on_response(boost::system::error_code const&, libtorrent::http_parser const&, char const*, int)+0x90 [0x37a102d120]
/usr/lib64/libtorrent-rasterbar.so.5 : boost::function5<void, boost::system::error_code const&, libtorrent::http_parser const&, char const*, int, libtorrent::http_connection&>::operator()(boost::system::error_code const&, libtorrent::http_parser const&, char const*, int, libtorrent::http_connection&) const+0x52 [0x37a100a7d2]
/usr/lib64/libtorrent-rasterbar.so.5 : libtorrent::http_connection::callback(boost::system::error_code const&, char const*, int)+0x1bf [0x37a1000fff]
/usr/lib64/libtorrent-rasterbar.so.5 : libtorrent::http_connection::on_resolve(boost::system::error_code const&, boost::asio::ip::basic_resolver_iterator<boost::asio::ip::tcp>)+0x440 [0x37a10014f0]
/usr/lib64/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::http_connection, boost::system::error_code const&, boost::asio::ip::basic_resolver_iterator<boost::asio::ip::tcp> >, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<libtorrent::http_connection> >, boost::arg<1>, boost::arg<2> > >, boost::system::error_code, boost::asio::ip::basic_resolver_iterator<boost::asio::ip::tcp> > >::do_call(boost::asio::detail::handler_queue::handler*)+0x239 [0x37a101c4f9]
/usr/lib64/libtorrent-rasterbar.so.5 : boost::asio::detail::task_io_service<boost::asio::detail::epoll_reactor<false> >::run(boost::system::error_code&)+0x339 [0x37a0f57a79]
/usr/lib64/libtorrent-rasterbar.so.5 : libtorrent::aux::session_impl::operator()()+0x81 [0x37a0f961b1]
/usr/lib64/libboost_thread-mt.so.5 : thread_proxy()+0x60 [0x37a060b670]
/lib64/libpthread.so.0() [0x37916068e0]
/lib64/libc.so.6 : clone()+0x6d [0x3790ee0c9d]
Segmentation fault (core dumped)
Original comment by wizardal...@gmail.com
on 23 Nov 2010 at 2:07
any chance someone could get a back trace out of gdb for this? with local
variables and the exact position where it crashes?
Original comment by arvid.no...@gmail.com
on 24 Nov 2010 at 11:56
Got the same crash, but on Windows and 0.15.8. Screen with trace attached. It's
quite a stable bug, so I can provide any additional info.
Original comment by Oleg.Shp...@gmail.com
on 20 Oct 2011 at 10:14
Attachments:
when does it happen?
Do you know what error the tracker hits when it happens?
Which object is invalid, to cause the crash. is the http_tracker_connection
object destructed by the time the callback is called?
Original comment by arvid.no...@gmail.com
on 20 Oct 2011 at 7:45
Original issue reported on code.google.com by
leigh123...@gmail.com
on 18 Feb 2010 at 2:12Attachments: