mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Frequent crashes #763
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#763
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 @pixecs on GitHub (Sep 22, 2013).
The qBittorrent v3.0.11 is crashing very frequent with this backtrace:
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
qBittorrent version: v3.0.11
stack trace:
/lib64/libc.so.6 : ()+0x35450 [0x7f326232e450]
/lib64/libcrypto.so.1.0.0 : RC4()+0x186 [0x7f326513d486]
Segmentation fault
qBittorrent buid against following libraries:
Qt: 4.8.4
Libtorrent: 0.15.10.0
Boost: 1.49.0
OS: openSUSE 12.3 (x86_64)
Kernel: Linux 3.7.10-1.4-desktop x86_64
KDE: 4.10.5 "release 1"
@oeilgauche commented on GitHub (Sep 26, 2013):
I think I have the exact same problem (in Ubuntu Server in my case), but I'm not sure how to access the backtrace to post it. Could you point me to a good source?
@srvanderplas commented on GitHub (Sep 26, 2013):
I am also having similar issues.
@sledgehammer999 commented on GitHub (Sep 26, 2013):
#750 and http://qbforums.shiki.hu/index.php/topic,2197.msg7992.html#msg7992