mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Caught signal: SIGSEGV #11958
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#11958
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 @riveravaldez on GitHub (Apr 1, 2021).
Hi, this bug appeared some time ago (can't remember how much) and I only have the information I took at the moment. If this is no relevant please discard it, right now qBittorrent seems to be working fine. Thanks a lot.
qBittorrent version and Operating System
qBittorrent version: v4.1.5, on Debian Testing
If on linux, libtorrent-rasterbar and Qt version
Don't have that data, sorry.
What is the problem
If I recall correctly, it was a crash. I got:
What is the expected behavior
Normal running. But after the crash it was normally restarted.
Steps to reproduce
Can't say.
Extra info(if any)
Doesn't seems to have happened again, maybe this is already fixed.
Thanks a lot. Best regards.
@thalieht commented on GitHub (Apr 1, 2021):
Duplicate of #9667. This was fixed long ago but thanks for the report.
@riveravaldez commented on GitHub (Apr 1, 2021):
Great. Thanks a lot and sorry for the delay... Kind regards!