You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
qbittorrent-nox 4.6.7 64-bit
qBittorrent was built with the following libraries:
Qt: 6.7.2
Libtorrent: 1.2.19.0
Boost: 1.86.0
OpenSSL: 3.3.2
zlib: 1.3.1.zlib-ng
What is the problem?
If "Delete .torrent files afterwards" is enabled, but the .torrent file is not where expected at the time the torrent finishes, the process crashes. This may affect the function that copies .torrent files afterwards as well.
Ideally, the error would be caught and logged, rather than crashing the process.
Steps to reproduce
Have the setting enabled
Start a torrent
Delete the .torrent file
When it finishes, the process crashes
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered:
If "Delete .torrent files afterwards" is enabled, but the .torrent file is not where expected at the time the torrent finishes
What .torrent file do you talk about?
"Delete .torrent files afterwards" is about source .torrent file. qBittorrent doesn't reference source .torrent files after torrent is added (it stores torrent metadata internally).
qBittorrent & operating system versions
qbittorrent-nox 4.6.7 64-bit
qBittorrent was built with the following libraries:
Qt: 6.7.2
Libtorrent: 1.2.19.0
Boost: 1.86.0
OpenSSL: 3.3.2
zlib: 1.3.1.zlib-ng
What is the problem?
If "Delete .torrent files afterwards" is enabled, but the .torrent file is not where expected at the time the torrent finishes, the process crashes. This may affect the function that copies .torrent files afterwards as well.
Ideally, the error would be caught and logged, rather than crashing the process.
Steps to reproduce
Have the setting enabled
Start a torrent
Delete the .torrent file
When it finishes, the process crashes
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: