mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Crash while downloading #4249
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#4249
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @classyyy on GitHub (May 3, 2016).
OS: uname -a
Linux 3.14.32-xxxx-grs-ipv6-64 #7 SMP Wed Jan 27 18:05:09 CET 2016 x86_64 GNU/Linux
cat /etc/*release
DISTRIB_ID=Debian
DISTRIB_RELEASE=8
DISTRIB_CODENAME=
DISTRIB_DESCRIPTION=
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
libtorrent version - 1.1.0
qBittorrent version - 3.3.4
(running qBittorrent-nox)
******** Information ********
To control qBittorrent, access the Web UI at http://localhost:8080
The Web UI administrator user name is: xxxx
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Catching signal: SIGABRT
Please file a bug report at http://bug.qbittorrent.org and provide the following information:
qBittorrent version: v3.3.4
stack trace:
/lib/x86_64-linux-gnu/libc.so.6 : gsignal()+0x37 [0x6d30dba76067]
/lib/x86_64-linux-gnu/libc.so.6 : abort()+0x148 [0x6d30dba77448]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : __gnu_cxx::__verbose_terminate_handler()+0x15d [0x6d30dc39232d]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d3b6 [0x6d30dc3903b6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d401 [0x6d30dc390401]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6 : ()+0x8d619 [0x6d30dc390619]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0x561ef [0x6d30dd7cb1ef]
/usr/lib/libtorrent-rasterbar.so.9 : libtorrent::torrent_alert::torrent_alert(libtorrent::aux::stack_allocator&, libtorrent::torrent_handle const&)+0x32e [0x6d30dd7e657e]
/usr/lib/libtorrent-rasterbar.so.9 : libtorrent::peer_alert::peer_alert(libtorrent::aux::stack_allocator&, libtorrent::torrent_handle const&, boost::asio::ip::basic_endpointboost::asio::ip::tcp const&, libtorrent::sha1_hash const&)+0x12 [0x6d30dd7e6612]
/usr/lib/libtorrent-rasterbar.so.9 : libtorrent::block_finished_alert::block_finished_alert(libtorrent::aux::stack_allocator&, libtorrent::torrent_handle, boost::asio::ip::basic_endpointboost::asio::ip::tcp const&, libtorrent::sha1_hash const&, int, int)+0x11 [0x6d30dd7e7141]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0x14fb26 [0x6d30dd8c4b26]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0x1496ab [0x6d30dd8be6ab]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0x14a5ab [0x6d30dd8bf5ab]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0xb3c04 [0x6d30dd828c04]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0xb4f1f [0x6d30dd829f1f]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0x19d364 [0x6d30dd912364]
/usr/lib/libtorrent-rasterbar.so.9 : ()+0xb4bcf [0x6d30dd829bcf]
/lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x80a4 [0x6d30dc6860a4]
/lib/x86_64-linux-gnu/libc.so.6 : clone()+0x6d [0x6d30dbb2987d]
@nmakeenkov commented on GitHub (Dec 9, 2016):
Exactly the same problem on start(stack trace is similar) on ubuntu 16.04, running qbittorrent v3.3.1 with libtorrent v1.0.7, boost v1.58.0
@ngosang commented on GitHub (Sep 16, 2018):
We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.