mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
crash when clicking on torrent in the list #10310
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#10310
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 @alex-tee on GitHub (Apr 27, 2020).
Please provide the following information
qBittorrent version and Operating System
qBittorrent v4.2.1, GuixSD GNU/Linux
If on linux, libtorrent-rasterbar and Qt version
libtorrent-rasterbar: 1.1.14
qtbase: 5.12.7
What is the problem
clicking on a specific torrent crashes
What is the expected behavior
no crash
Steps to reproduce
click on a specific torrent
Extra info(if any)
@FranciscoPombal commented on GitHub (Apr 27, 2020):
https://github.com/qbittorrent/qBittorrent/blob/master/CONTRIBUTING.md
In addition, use libtorrent 1.2.x, 4.2.x with libtorrent 1.1.x has been untested for a long time and support for libtorrent 1.1.x will be removed soon.
@Chocobo1 commented on GitHub (Apr 29, 2020):
@FranciscoPombal
Please don't dismiss reports too quickly. This one is interesting and the relevant code isn't much different between recent versions.
Also the rational you provided would falsely label this case into "true negative".
@xavier2k6 commented on GitHub (Feb 27, 2021):
@Chocobo1 Are you still interested in this or can it be locked now?
@Chocobo1 commented on GitHub (Feb 27, 2021):
PR #12692 should have handled it.