Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Please provide the following information
qBittorrent version and Operating System
Windows 10 Pro / 64 latest updates
What is the problem
If i exit during downloads, on restart i get all torrents as red with "Missing Files" and in the log i see:
(this is introduced in the beta, 4.1.9 doesn't experience this)
ATTENTION: This beta release uses the libtorrent 1.2.x series. It saves fastresumes a bit differently than the 1.1.x series, which are used so far in the stable versions (and alpha releases). If you run it and then downgrade to a previous qBittorrent version then your torrents will probably start rechecking.
please recheck your torrents manually or force resume which will do the checking anyway & report back.
also it is not advisable to exit qBittorrent while still downloading, you should first pause......wait until no more activity 0 bytes up/down & then exit to make sure it exits cleanly/still not trying to read/write data...
@xavier2k6 I do understand fully what you say, i had to re-read the whole thing.
The problem apparently with the beta version is that i exit while downloading. As i posted that doesn;'t cause any problem with 4.1 version and also with ANY other torrent client.
Other clients also when you exit, they AUTO stop or pause before exiting. You don't need to manually pause or stop anything.
I don't believe qbittorrent AUTO stops/pauses before exiting - open to correction on that.
4.2.0 Beta 1 introduced a new version of libtorrent which at least pieces field format changed in .fastresume, libtorrent 1.2 -> libtorrent 1.1 leads to re-hashing...
There were other changes too on that front & also as with any other "Beta" it's to be considered unstable.....checking has underwent some other changes since the beta as it wasn't fully finalised.
Anyway.......back on-topic, can you go to %LOCALAPPDATA%\qBittorrent\BT_backup & check your .fastresume files against your .torrent files & make sure they match/equal amount. eg 500 .fastresume files/500 .torrent files
If all ok & nothing extra/missing->open qbittorrent>pause ALL->wait for no data transmission up or down->force resume ALL briefly for about 2 seconds & re-pause.
This should save all .fastresume files with same modified date/time -> this should resolve any checking issues or hopefully mitigate the issue.
As you can see above - I referenced this issue in the 4.2.0 final release plan to be looked into & if issue remains after the RC(with hopefully finalised checking commits) - flag it again there...