qBittorrent suffers with slight amnesia.

[Legendarion]

qBittorrent & operating system versions

Windows 10 Home x64 22H2 (10.0.19045)

qBittorrent 4.6.5 x64

Qt: 6.4.3
Libtorrent: 2.0.11.0
Boost: 1.85.0
OpenSSL: 1.1.1w
zlib: 1.3.1

What is the problem?

The program suffers with slight amnesia from time to time.
One example is when I have stopped all torrents from being Seeding to Completed (marked all with CTRL + A and then stopped all torrents), then closing qB and then start the computer hours later after being turned off, the program, for some reason in this case, have 14 torrents seeding while the rest stays as Completed.

The other example are that in some bizarr occasions it re-check a torrent by itself after starting the program.

Not something that happens every day or each week, but maybe 2-4 times within a month.

Log(s) & preferences file(s)

12.07.2024 20:24 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Mon Jul 1 02:34:52 2024.
12.07.2024 20:24 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using UPnP. local: XXX.XXX.X.XX external port: UDP/6332"
12.07.2024 20:24 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using UPnP. local: XXX.XXX.X.XX external port: TCP/6332"
12.07.2024 20:24 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using NAT-PMP. local: 192.168.0.41 external port: UDP/6332"
12.07.2024 20:24 - UPnP/NAT-PMP port mapping succeeded. Message: "successfully mapped port using NAT-PMP. local: 192.168.0.41 external port: TCP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "::1". Port: "UTP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "::1". Port: "TCP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "fe80::eec4:85ea:5292:57c3%4". Port: "UTP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "fe80::eec4:85ea:5292:57c3%4". Port: "TCP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "XXX.XXX.X.XX". Port: "UTP/6332"
12.07.2024 20:24 - Successfully listening on IP. IP: "XXX.XXX.X.XX". Port: "TCP/6332"
12.07.2024 20:24 - UPnP/NAT-PMP support: ON
12.07.2024 20:24 - Encryption support: ON
12.07.2024 20:24 - Anonymous mode: OFF
12.07.2024 20:24 - Peer Exchange (PeX) support: ON
12.07.2024 20:24 - Local Peer Discovery support: ON
12.07.2024 20:24 - Distributed Hash Table (DHT) support: ON
12.07.2024 20:24 - HTTP User-Agent: "qBittorrent/4.6.5"
12.07.2024 20:24 - Peer ID: "-qB4650-"
12.07.2024 20:24 - Trying to listen on the following list of IP addresses: "0.0.0.0:6332,[::]:6332"
12.07.2024 20:24 - Using config directory: C:\Users\AppData\Roaming\qBittorrent
12.07.2024 20:24 - qBittorrent v4.6.5 started

[Destroyarr]

Try chkdsk c: /f /x (will work during next boot up)

export all torrents

Reinstall clean qbt

import all torrents and reseed (you can select without recheck)

Report after few weeks when exactly with more context when problems occur

If some problems are easily manageable try to manage them manually let the app have few quirks

However report hem with context when they happen

[HanabishiRecca]

That behavior occurs when the client was not exited gracefully.
E.g. if you click exit button and then shutdown the PC immediately, the process could be killed prematurely. Because the client needs time to send stop requests to all trackers and then save the data.
In which case, do not shutdown immediately. Open the Task Manager and wait until qBittorrent process is gone.

[glassez]

Because the client needs time to send stop requests to all trackers and then save the data.

This is not quite correct. In fact, it does this in parallel, so that data saving can be done much faster than all "stop" requests are processed.

[Legendarion]

HanabishiRecca: I am aware that the program need some time, but there are cases when letting the program stay a little while and then exiting it, it can occur for no particular reason. At least for me.

Like I said it's not something that happens often, but maybe 2-4 times within the month. Or less for that matter. But from time to time it can be a little bit annoying especially if you have a lot of torrents.

[Destroyarr]

@Legendarion sorry its not clear the context of the issue.

Knowing how things are supposed to work, highest probable is indeed the qbitorrent.exe was still running in Task Manager: details, when it was forcefully killed by a shutdown/restart.

There is no other cogent explanation with the provided observed behavior.

[Legendarion]

Well, nevertheless, I'll let the thread live on and see if other could suffer the same.

[luzpaz]

Can someone propose a less generic name for the ticket that succinctly captures what the issue is ?

[Destroyarr]

"Sometimes Seeding some torrents which were previously Stopped"

Could it be CtrlA selection was done, while the list is filtered by Status/Categories/Tags/Trackers ? @Legendarion

[Destroyarr]

Reporter could be experiencing general thread hold-up issue as others are.