qbittorrent-2.0.0 crashes on adding / starting torrent

[leigh123linux]

Warning: Local domain socket was not closed cleanly, deleting file...

*************************************************************
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
stack trace:
  /lib64/libc.so.6() [0x350b833790]
  /usr/lib64/libtorrent-rasterbar.so.5 : libtorrent::peer_connection::on_receive_data(boost::system::error_code const&, unsigned long)+0x246 [0x351bf1bb26]
  /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::peer_connection, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_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 [0x351bf23348]
  /usr/lib64/libtorrent-rasterbar.so.5 : boost::asio::detail::task_io_service<boost::asio::detail::epoll_reactor<false> >::run(boost::system::error_code&)+0x339 [0x351bf358b9]
  /usr/lib64/libtorrent-rasterbar.so.5 : libtorrent::aux::session_impl::operator()()+0x81 [0x351bf73401]
  /usr/lib64/libboost_thread-mt.so.5 : thread_proxy()+0x60 [0x351980b670]
  /lib64/libpthread.so.0() [0x350c006aea]
  /lib64/libc.so.6 : clone()+0x6d [0x350b8e22dd]

[leigh123linux (leigh123linux-deactivatedaccount)]

More info

O/S = F13
QT = 4.6 final
libtorrent = 0.14.7

[Christophe Dumez (hydr0g3n)]

Well, this is in libtorrent code. Nothing I can do except forward to the author.

[leigh123linux (leigh123linux-deactivatedaccount)]

The same libtorrent version works OK in F12

[root@localhost leigh]# rpm -q qbittorrent rb_libtorrent qt
qbittorrent-2.0.0-1.fc12.x86_64
rb_libtorrent-0.14.7-1.fc12.x86_64
qt-4.5.3-9.fc12.x86_64
[root@localhost leigh]#

I will try rebuilding libtorrent to see if it fixes the issue.

[leigh123linux (leigh123linux-deactivatedaccount)]

Bug reported here as well

https://bugzilla.redhat.com/show_bug.cgi?id=547335