SABnzbd Forums

Noticed this a couple of times.
If my disk is full sabnzbd will stop downloading. In some cases i want to "force" to finish (the last active) download. So i change the priority of *only this* item.

You expect sabnzbd to stop after this download, but it seems there are corner cases:
* if you have multiple newservers and the primary is done (and the secondary newservers are queried/busy). Sabnzbd will start the following download (which has a normal/high priority)
* About the next one not really sure. Thought i saw issues with long unpacking and/or sending back to the queue (and thus starting next download items). But i can not confirm this at this point.

That's correct. You can turn on Download top job only (forgot the exact name right now) in Config Switches.
This will stop this, but also not allow multiple server usage in normale cases.

You are probably referring to "Only Get Articles for Top of Queue" with explanation "Enable for less memory usage. Disable to prevent slow jobs from blocking the queue."

This somewhat sounds like a "workaround". In my opinion this is a bug in the multi-threading model. And it is not *blocking* the queue it is that it is *continuing* items in the queue what is dangerous. To be fair, i can understand this can be tricky to solve but imho a bug issue is warranted?

It's indeed a known issue that has performance impact to solve, so we didn't implement it.
I should have mentioned that in my first response!