Hashchecking Randomly?

[teddyrogers]

Tribler 8.1.2, with, "Check torrent after completion", enabled, after Tribler is re/started, hashchecking is performed on some already completed and previously hash checked files. I do not know what prompts "random" torrents to be chosen for another hash check.

I think a better way to prevent hash checks recurring unnecessarily would be a flag in the dlcheckpoints file, after a torrent has completed and hash checked. The only occasions where any further hash checks need to be performed is when the user requests it.

[qstokkink]

Assuming you know how to operate the debug tab, the logs should provide insight into what is happening.

If a torrent is skipped for rechecking, the following message appears:

tribler/src/tribler/core/libtorrent/download_manager/download.py

Line 190 in d226d92

self._logger.info("Skipping recheck of %s, already finished when added!", str(self))

If a torrent is scheduled for rechecking, this message appears instead:

tribler/src/tribler/core/libtorrent/download_manager/download.py

Line 193 in d226d92

self._logger.info("Force rechecking %s after completion!", str(self))

If you see any Force rechecking <<download details here>> after completion! messages just after starting (in between other Skipping recheck of <<download details here>>, already finished when added!), we know where to look. If these messages are not there, something else entirely may be going on.

[teddyrogers]

Unfortunately I can't view the logs because of this issue: #8478

Some of the completed torrents do not get hash checked again after multiple Tribler restarts. Then for some random reason on a subsequent restart the torrent is checked again.

[absolutep]

Tribler 8.1.2, with, "Check torrent after completion", enabled, after Tribler is re/started, hashchecking is performed on some already completed and previously hash checked files. I do not know what prompts "random" torrents to be chosen for another hash check.

I think a better way to prevent hash checks recurring unnecessarily would be a flag in the dlcheckpoints file, after a torrent has completed and hash checked. The only occasions where any further hash checks need to be performed is when the user requests it.

I told you bro, last month by giving example of BiglyBT that this feature is nothing but inviting trouble on your own self.