starred/qBittorrent

Fork 0

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

qBittorrent 3.3.1 does not close completely in Windows 8.1 Pro #3478

New issue

Closed

opened 2026-02-21 16:47:50 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-21 16:47:50 -05:00

Owner

Originally created by @jpBenfica on GitHub (Dec 7, 2015).

After closing is running in the background on the task manager, for a few minutes.

Originally created by @jpBenfica on GitHub (Dec 7, 2015). After closing is running in the background on the task manager, for a few minutes.

deekerman closed this issue

2026-02-21 16:47:53 -05:00

deekerman commented

2026-02-21 16:47:55 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Dec 7, 2015):

How many torrents do you have in your list?

@sledgehammer999 commented on GitHub (Dec 7, 2015): How many torrents do you have in your list?

deekerman commented

2026-02-21 16:47:56 -05:00

Author

Owner

@jpBenfica commented on GitHub (Dec 7, 2015):

4 torrents

@jpBenfica commented on GitHub (Dec 7, 2015): 4 torrents

deekerman commented

2026-02-21 16:47:56 -05:00

Author

Owner

@jpBenfica commented on GitHub (Dec 7, 2015):

uTorrent, Bittorrent and Deluge have the same problem.

@jpBenfica commented on GitHub (Dec 7, 2015): uTorrent, Bittorrent and Deluge have the same problem.

deekerman commented

2026-02-21 16:47:56 -05:00

Author

Owner

@direwolfie commented on GitHub (Dec 8, 2015):

After closing is running in the background on the task manager, for a few minutes.

See if any files are being "re/checked" by the client. It will first finish checking and only then close the client completely (as far as I have seen). All the above torrent clients do that.
This could also happen if there are a lot of torrents and it has to save their current download state. And this would largely depend on the number of torrents you are downloading. (although I might be wrong about this one)

@direwolfie commented on GitHub (Dec 8, 2015): > After closing is running in the background on the task manager, for a few minutes. See if any files are being "re/checked" by the client. It will first finish checking and only then close the client completely (as far as I have seen). All the above torrent clients do that. This could also happen if there are a lot of torrents and it has to save their current download state. And this would largely depend on the number of torrents you are downloading. (although I might be wrong about this one)

deekerman commented

2026-02-21 16:47:56 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 25, 2016):

Sometimes, dns requests (or generally network requests) make libtorrent wait a long time. It could be a combination of network drivers/network hardware/OS/actual network responsiveness

@sledgehammer999 commented on GitHub (Jan 25, 2016): Sometimes, dns requests (or generally network requests) make libtorrent wait a long time. It could be a combination of network drivers/network hardware/OS/actual network responsiveness

deekerman commented

2026-02-21 16:47:56 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 25, 2016):

Does it still happen with v3.3.3?

@sledgehammer999 commented on GitHub (Jan 25, 2016): Does it still happen with v3.3.3?

deekerman commented

2026-02-21 16:47:56 -05:00

Author

Owner

@direwolfie commented on GitHub (Jan 26, 2016):

It has started happening for me as well. Takes about 30-60 seconds for qBittorrent to close after closing the UI.
The 2 systems that I have the issue with -

Linux Mint 17.2 x64 MATE running client v.3.3.1
Debian Jessie x32 running client v3.1.10

I suspect that the problem is with the OS or packages qBittorrent depends on, because I did not have this problem earlier on Debian. And I have tried qBittorrent on other networks, so definitely not a network thing (unless its a country wide network issue :) ).

@direwolfie commented on GitHub (Jan 26, 2016): It has started happening for me as well. Takes about 30-60 seconds for qBittorrent to close after closing the UI. The 2 systems that I have the issue with - 1. Linux Mint 17.2 x64 MATE running client v.3.3.1 2. Debian Jessie x32 running client v3.1.10 I suspect that the problem is with the OS or packages qBittorrent depends on, because I did not have this problem earlier on Debian. And I have tried qBittorrent on other networks, so definitely not a network thing (unless its a country wide network issue :) ).

deekerman commented

2026-02-21 16:47:56 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Jan 26, 2016):

It may depend on your libtorrent/boost.asio version...
In any case, I don't think qbittorrent can fix this nor that it is our problem, so I am closing this.
We can reconsider when more precise info/observations arise.

@sledgehammer999 commented on GitHub (Jan 26, 2016): It may depend on your libtorrent/boost.asio version... In any case, I don't think qbittorrent can fix this nor that it is our problem, so I am closing this. We can reconsider when more precise info/observations arise.