search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
27.42k stars 3.9k forks source link

the *other* stalled problem #8697

Open iansebryk opened 6 years ago

iansebryk commented 6 years ago

Please provide the following information

qBittorrent version and Operating System

4.0.4 on Win10 Pro (10.0.1xxxx)

What is the problem

torrents have stalled but will not allow queue to progress. in other words, other torrents that CAN download ARE NOT. currently have 6 items in queue. max DLs is set to 5. top 5 are stalled, 6th won't start. which is retarded because if i stack a bunch of torrents and the first few tank, then the rest just sit there FOR DAYS (if i'm away) when they should have downloaded and seeded.

What is the expected behavior

if a torrent is stalled (for whatever reason), the subsequent queued torrents should start downloading, if possible. stalled torrents should not prevent the rest of the torrent queue from being processed. THIS IS STANDARD BEHAVIOUR IN EVERY OTHER CLIENT.

Steps to reproduce

(type here)

Extra info(if any)

if i push (using previous example) the 6th torrent up into the 5, it starts normally. if i then move it down, it changes back to 'queued' status and stops... while the entire stack above is stalled. due to bandwidth restrictions, i can't set the max to more than 8, so if i have 9 queued, that 9th is just sitting there like a dopey log whereas it should just start.

thalieht commented 6 years ago

Options -> BitTorrent -> Do not count slow torrents in these limits

iansebryk commented 6 years ago

already checked. :) but thank you.

thalieht commented 6 years ago

FYI that option respects the Max active torrents in torrent queueing and won't open new slots beyond that number.

iansebryk commented 6 years ago

i appreciate that, and that's to be expected. HOWEVER. if a torrent is stalled, it is effectively off, paused, stopped or otherwise not functioning. so holding up the queue that COULD be running is anathema. and effectively means i have to be constantly monitoring my queue. which i don't want to do nor have i had to with every other client. 👎

troodonic commented 6 years ago

I observe the same behavior as iansesbryk does, and feel the same way about it. It makes the application useless. There are no FYI considerations to be made.

Seeker2 commented 6 years ago

After 5-60 minutes, stalled torrents should return to a queued state and other torrents that have at least a remote chance of working should start (quit being just queued) in their place. This way, the active torrents limit won't be exceeded but stalled jams won't block everything else.

iansebryk commented 6 years ago

yeah... except it doesn't. i've watched a stack sit all day waiting... the stalled torrents never demote to queued status.

Seeker2 commented 6 years ago

Sorry, I don't mean qBitTorrent is currently programmed to work that way. I mean it should be fixed to work that way. The current behavior, while maybe "working as designed", is simply broken in terms of how people EXPECT it to work.

iansebryk commented 6 years ago

ah! gotcha! yes, absolutely. it kinda makes qBT pretty useless if you have a pokey torrent or twelve... ;)

ankushnarula commented 5 years ago

For me, the problem was that I was sharing to a remembered path on my network but the network share had not been accessed since reboot (even though it appeared connected in the macOS Finder).

+1 for better handling of disk errors