Improve auto exit after download/seed finish.

[lelicopter]

Improve auto exit after download/seed finish.

[thalieht]

if the torrent file has already been downloaded, the torrent still receives traffic for some time

If you're talking about the download speed then there is no traffic once downloaded. These numbers are 5 sec rolling averages.

and despite auto-deletion, it remains in the list until the next launch.

If you're talking about the "Seeding limits" action, torrents are checked every 10 seconds whether they fulfill the criteria.

[lelicopter]

OK! I will try to record a video for this situation soon to make it more clear.

[lelicopter]

important setting.
video will be later.

[lelicopter]

https://youtu.be/m3pK4DLA6eQ?t=32
(from 32 second)

After the download is completed, the first torrent continues to receive traffic for a few more seconds, only then the task is removed from the list.

If the immediate exit mode upon completion of downloads is enabled, then this task is not removed from the list because it continues to receive traffic, but the application has already completed its work considering the downloads completed.

If you wait for the timer to count down when exiting, the task will have time to receive all the extra traffic and will be correctly removed from the list before the application exits.

[lelicopter]

there is no traffic once downloaded. These numbers are 5 sec rolling averages.

watch the video please. I mean this "extra traffic" before deleting the torrent (it may not be real traffic, but it freezes the task in the queue for a while and blocks its deletion before exiting the application).

[glassez]

watch the video please. I mean this "extra traffic" before deleting the torrent (it may not be real traffic, but it freezes the task in the queue for a while and blocks its deletion before exiting the application).

If you still didn't understand @thalieht's answer, there is no "extra traffic" that "freezes the task in the queue for a while and blocks its deletion before exiting the application". There is just 10sec timeout between subsequential "seeding limits" processings so it doesn't have time to fire before exiting the application.

Seems it could make sense to trigger "seeding limits" processing on "torrent finished" event.

[lelicopter]

If you still didn't understand @thalieht's answer, ...

it may be called a unicorn horn, but that doesn't solve the problem. auto-delete doesn't work.

[glassez]

If you still didn't understand @thalieht's answer, ...

it may be called a unicorn horn, but that doesn't solve the problem. auto-delete doesn't work.

They just tried to explain to you how it works (it doesn't work in real time). I believe "auto-delete" will trigger the next time you run qBittorrent.

In any case, why continue these bickering, given that it should be fixed by #20917?..

[lelicopter]

I believe "auto-delete" will trigger the next time you run qBittorrent.

In case the file was deleted after 1) the download was completed, 2) when the application was automatically closed, 3) the torrent should have been deleted 0 minutes after the seed, but remained in the queue until exited. The next time you run it, qBittorent shows an error that the file does not exist, highlights the torrent in red, and never removes it from the list.

Thus, deleting a file while qBittorent is not running causes auto-delete to not work if auto-close without a countdown timer is used.

That is, I downloaded a file, I want to automatically remove it from the list of torrents at the end of the download, without distributing it. I want qBittorent to close automatically without countdown. And as a result, I'm not allowed to delete the downloaded file until I run qBittorent again, otherwise the torrent will remain listed until I manually delete it. It turns out to be a strange illogical restriction that breaks the auto-removal of torrents from the list.