mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Torrent priorities change every time I start qBittorrent #7802
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#7802
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 @ZucriyAmsuna on GitHub (Sep 21, 2018).
Windows 7 Home Premium, Service Pack 1 64-bit
qBittorrent v4.1.3 (or all of them within the past few years)
When downloading multiple torrents, you can shift them around to change their priority using the up/down arrows in the toolbar. I always have my torrents sorted in this manner, with 1 at the top.
However, upon restarting qBittorrent, these priorities change randomly. Many of the torrents stay generally where they were before, but some torrents move from near the top to the bottom of the list or vice versa.
It's a pain to deal with, especially with my slower Internet and only downloading a few torrents at a time. Every time I start it up, I must find the torrents I want to download first and re-prioritize them.
This issue has existed since I started using qBittorrent about three years ago (starting shortly after when uBittorrent was discovered to have been using computer resources to mine bitcoins).
@thalieht commented on GitHub (Sep 21, 2018):
I assume you have paused torrents. Do you delete any torrent that is in the queue (unfinished) before restarting qBt and torrents lose their priorities? If yes do you remember if there was a time that you didn't delete but it still lost priorities (with 4.1.2 only, not before)?
@ZucriyAmsuna commented on GitHub (Sep 21, 2018):
Very rarely do I pause a torrent. I do occasionally delete unfinished torrents, but it's not that often. The priorities change every single time I restart it after I re-prioritize them. If I don't move any of them around, then they stay the same with each restart.
(For clarification: Don't get the file priorities mixed up with the torrent priorities. I'm only talking about the torrent priorities with the arrows in the toolbar, not the normal/high/maximum file priorities within each single torrent.)
Edit: I'll give an example. Let's say I have five torrents downloading (and any number finished and uploading). They are prioritized as follows: 1=A, 2=B, 3=C, 4=D, 5=E. I leave them alone, close qBt, open qBt, and they remain. No issues. I move E up two levels. 1=A, 2=B, 3=E, 4=C, 5=D. Close qBt. Open qBt. As the torrents load into view, they change positions to something like this: 1=A, 2=C, 3=B, 4=E, 5=D.
This also happens whenever I add a new torrent and move it from the default bottom priority to the top. After closing and reopening qBt, the new torrent moves back down near the bottom.
@glassez commented on GitHub (Sep 22, 2018):
@ZucriyAmsuna, have you any paused torrent in your queue? Have you message about "corrected torrents positions" in application log?
@ZucriyAmsuna commented on GitHub (Sep 22, 2018):
No paused torrents. The Execution Log has the following lines in red:
Queue positions were corrected in 41 resume files.
Unable to resume torrent '[torrent hash here]'
Unable to...
Unable to...
...
There are seven total torrents that could not be resumed, and none of them are being downloaded anymore. I deleted them months or even years ago. I cannot recall if they were finished when I deleted them.
The rest of the log looks pretty normal.
@1024mb commented on GitHub (Dec 22, 2018):
This is happening to me too, and it's been a long time since it's happening. I got 755 torrents paused (incompletes) and every time I add 1 or more torrent and restart the app the queue gets randomly sorted, same as OP, not every torrent gets sorted but a lot of them do. There is nothing abnormal in the log except for this line: Queue positions were corrected in 95 resume files
I got that every single time I open qBittorrent and some others that say: Fast resume data was rejected for torrent 'XYZ'. Reason: XYZ fast resume rejected. stat(XYZ\DUPLICATE\MKB_RO.inf): mismatching file timestamp. Checking again....
And the curious thing about that is that I've never resumed that torrent, I mean, it is empty, qB hasn't downloaded anything from that torrent, I don't know what the program expects to check.
It is annoying because I have to search between 750+ torrents for the one(s) I've added last.
@thalieht commented on GitHub (Dec 22, 2018):
Should be fixed by #9883, will be in 4.1.5.