mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
qb 2.9.8 random seg fault out of the blue. #774
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#774
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 @133794m3r on GitHub (Sep 27, 2013).
Couldn't set environment variable...
Peer ID: -qB2980-
HTTP user agent is qBittorrent v2.9.8
Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
qBittorrent version: v2.9.8
stack trace:
/lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0 [0x7f6d6d4d54f0]
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7f6d700af7bd]
Segmentation fault
I don't know what else to say about it, this just randomly started happening out of the blue. This just started happening without any warnings. I can't figure out why it's doing this either.
@133794m3r commented on GitHub (Sep 27, 2013):
apparently this is known already with debian so I'm going to close this issue since this only happens with QB, and the issue doesn't effect deluge I'm just going to use that client instead because I prefer non-random crashes.
@sledgehammer999 commented on GitHub (Sep 30, 2013):
#750 and http://qbforums.shiki.hu/index.php/topic,2197.msg7992.html#msg7992