starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

qBittorrent suffers with slight amnesia. #15905

New issue

Closed

opened 2026-02-22 02:36:39 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-22 02:36:39 -05:00

Owner

Originally created by @Legendarion on GitHub (Jul 12, 2024).

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.

Originally created by @Legendarion on GitHub (Jul 12, 2024). ### 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.

deekerman

2026-02-22 02:36:39 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@ghost commented on GitHub (Aug 20, 2024):

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

@ghost commented on GitHub (Aug 20, 2024): 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

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@HanabishiRecca commented on GitHub (Aug 20, 2024):

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.

@HanabishiRecca commented on GitHub (Aug 20, 2024): 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.

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@glassez commented on GitHub (Aug 20, 2024):

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.

@glassez commented on GitHub (Aug 20, 2024): > 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.

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@Legendarion commented on GitHub (Aug 20, 2024):

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.

@Legendarion commented on GitHub (Aug 20, 2024): 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.

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@ghost commented on GitHub (Aug 21, 2024):

@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.

@ghost commented on GitHub (Aug 21, 2024): @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.

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@Legendarion commented on GitHub (Aug 21, 2024):

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

@Legendarion commented on GitHub (Aug 21, 2024): Well, nevertheless, I'll let the thread live on and see if other could suffer the same.

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@luzpaz commented on GitHub (Aug 21, 2024):

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

@luzpaz commented on GitHub (Aug 21, 2024): Can someone propose a less generic name for the ticket that succinctly captures what the issue is ?

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@ghost commented on GitHub (Aug 21, 2024):

"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

@ghost commented on GitHub (Aug 21, 2024): "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

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@ghost commented on GitHub (Aug 23, 2024):

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

@ghost commented on GitHub (Aug 23, 2024): Reporter could be experiencing general thread hold-up issue as others are.

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@Legendarion commented on GitHub (Nov 4, 2024):

My first post was probably not the best explanation, but this one kind of explains what I was trying to point out: https://github.com/qbittorrent/qBittorrent/issues/21766

@Legendarion commented on GitHub (Nov 4, 2024): My first post was probably not the best explanation, but this one kind of explains what I was trying to point out: https://github.com/qbittorrent/qBittorrent/issues/21766

deekerman commented

2026-02-22 02:36:48 -05:00

Author

Owner

@thalieht commented on GitHub (Nov 4, 2024):

My first post was probably not the best explanation, but this one kind of explains what I was trying to point out: https://github.com/qbittorrent/qBittorrent/issues/21766

So duplicate of #13556 #13826 #20562 and probably others. Can't decide which one to keep...

@thalieht commented on GitHub (Nov 4, 2024): >My first post was probably not the best explanation, but this one kind of explains what I was trying to point out: https://github.com/qbittorrent/qBittorrent/issues/21766 So duplicate of #13556 #13826 #20562 and probably others. Can't decide which one to keep...