qBittorent still not shutting down properly

deekerman commented

2026-02-21 19:06:06 -05:00

Owner

Originally created by @RCarlsonMD on GitHub (Aug 24, 2018).

Please provide the following information

qBittorrent version and Operating System

Any version of QB since 4.xxxx, Windows 10 latest updates

If on linux, libtorrent and Qt version

(type here)

What is the problem

QB GUI closes but leaves a process running indefinitely. Problem duplicated on many Win 10 desktops and notebooks.

When trying to restart QB, the GUI won't start a second time without rebooting.

This has been going on a long time with QB.

Even if it's a Libtorrent bug, it STILL needs to be fixed. Just closing the topic is not any sort of solution.

What is the expected behavior

Clean exit and restart.

Steps to reproduce

(type here)

Extra info(if any)

(type here)

Originally created by @RCarlsonMD on GitHub (Aug 24, 2018). **Please provide the following information** ### qBittorrent version and Operating System Any version of QB since 4.xxxx, Windows 10 latest updates ### If on linux, libtorrent and Qt version (type here) ### What is the problem QB GUI closes but leaves a process running indefinitely. Problem duplicated on many Win 10 desktops and notebooks. When trying to restart QB, the GUI won't start a second time without rebooting. This has been going on a long time with QB. Even if it's a Libtorrent bug, it STILL needs to be fixed. Just closing the topic is not any sort of solution. ### What is the expected behavior Clean exit and restart. ### Steps to reproduce (type here) ### Extra info(if any) (type here)

deekerman

2026-02-21 19:06:06 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@WhosAsking commented on GitHub (Aug 25, 2018):

I've noted a number of these complaints in the past, and based on my personal experience, I think one of the most likely causes is a torrent gone bad. If it's possible, obtain fresh downloads of all your active torrents, then delete them from qBittorrent (you can save the local data), then add them back in using the torrent files. If you preserved the local data, the torrent should check itself then resume where it left off.

Does this problem persist even with NO torrents?

@WhosAsking commented on GitHub (Aug 25, 2018): I've noted a number of these complaints in the past, and based on my personal experience, I think one of the most likely causes is a torrent gone bad. If it's possible, obtain fresh downloads of all your active torrents, then delete them from qBittorrent (you can save the local data), then add them back in using the torrent files. If you preserved the local data, the torrent should check itself then resume where it left off. Does this problem persist even with NO torrents?

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@RoadTrain commented on GitHub (Aug 26, 2018):

After update to 4.1.2.99~201808180832, it doesn't shut down cleanly on Linux Mint 18.
libtorrent 1.1.9+git20180812

@RoadTrain commented on GitHub (Aug 26, 2018): After update to 4.1.2.99~201808180832, it doesn't shut down cleanly on Linux Mint 18. libtorrent 1.1.9+git20180812

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@TheOne320 commented on GitHub (Sep 21, 2018):

I have the exact same problem. It bugs me a lot. Someone suggested deleting the whole torrent list. I have >400 Torrents running and do not want to all add them all back afterwards. Will this ever be fixed? I can provide as much information as needed.
Windows Pro x64 1803 with qBittorrent 4.1.3 x64
GUI closes but it stays open in Task Manager. No CPU usage.

@TheOne320 commented on GitHub (Sep 21, 2018): I have the exact same problem. It bugs me a lot. Someone suggested deleting the whole torrent list. I have >400 Torrents running and do not want to all add them all back afterwards. Will this ever be fixed? I can provide as much information as needed. Windows Pro x64 1803 with qBittorrent 4.1.3 x64 GUI closes but it stays open in Task Manager. No CPU usage.

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@thalieht commented on GitHub (Sep 21, 2018):

If you are willing, you can do what says here https://github.com/qbittorrent/qBittorrent/issues/5097#issuecomment-208048460 and post the output in that issue which is watched by the devs.
Duplicate of #5097

@thalieht commented on GitHub (Sep 21, 2018): If you are willing, you can do what says here https://github.com/qbittorrent/qBittorrent/issues/5097#issuecomment-208048460 and post the output in that issue which is watched by the devs. Duplicate of #5097

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@TheOne320 commented on GitHub (Sep 21, 2018):

Ok I did that.

@TheOne320 commented on GitHub (Sep 21, 2018): Ok I did that.

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@jrmain commented on GitHub (Oct 17, 2018):

Just started using qBittorrent, running it on Windows 8.1 64 bit. If I start qBittorrent, then close it without doing anything, the qbittorrent.exe process stops running. If I use qBittorrent to download something, once it's done and I close qBittorrent, the qbittorrent.exe process continues to run.

I often start qBittorrent by opening a .magnet or .torrent file from some other application, such as Firefox or DuckieTV, which may be part of the problem. I'll try starting it directly to see if that helps.

Note that I also have several stopped torrents permanently in my torrent list, which I use for testing; these are unlikely to be the problem, because qBittorrent closes fine with those torrents in the list as long as I haven't done any actual downloading.

@jrmain commented on GitHub (Oct 17, 2018): Just started using qBittorrent, running it on Windows 8.1 64 bit. If I start qBittorrent, then close it without doing anything, the qbittorrent.exe process stops running. If I use qBittorrent to download something, once it's done and I close qBittorrent, the qbittorrent.exe process continues to run. I often start qBittorrent by opening a .magnet or .torrent file from some other application, such as Firefox or DuckieTV, which may be part of the problem. I'll try starting it directly to see if that helps. Note that I also have several stopped torrents permanently in my torrent list, which I use for testing; these are unlikely to be the problem, because qBittorrent closes fine with those torrents in the list as long as I haven't done any actual downloading.

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@Tri125 commented on GitHub (Nov 13, 2018):

I'm running a freshly installed and up to date windows 7 64 machine.

I can independently confirm what jrmain observed.

Just like RCarlsonMD I also observed that the issue started to happen in the 4.x.x branch. I reported the issue back in February 2018 in #8157.

@Tri125 commented on GitHub (Nov 13, 2018): I'm running a freshly installed and up to date windows 7 64 machine. I can independently confirm what jrmain observed. Just like RCarlsonMD I also observed that the issue started to happen in the 4.x.x branch. I reported the issue back in February 2018 in #8157.

deekerman commented

2026-02-21 19:06:12 -05:00

Author

Owner

@jrmain commented on GitHub (Nov 14, 2018):

I've tried disabling all the options related to the notification area but it didn't help.

@jrmain commented on GitHub (Nov 14, 2018): I've tried disabling all the options related to the notification area but it didn't help.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@Tri125 commented on GitHub (Mar 11, 2019):

I've been banned from their subreddit for trying to talk about the issue. I was told that "It works on my machine so you're making things up" (paraphrasing a bit). That's a very unprofessional attitude to have in regard to software development as a whole. Ignoring a bug for an entire year is something but silencing users trying to bring attention to the issue is crossing a line. I expected better.

If the devs aren't running the subreddit, then they should be aware that the guys that do are damaging their brand.

@Tri125 commented on GitHub (Mar 11, 2019): I've been banned from their subreddit for trying to talk about the issue. I was told that "It works on my machine so you're making things up" (paraphrasing a bit). That's a very unprofessional attitude to have in regard to software development as a whole. Ignoring a bug for an entire year is something but silencing users trying to bring attention to the issue is crossing a line. I expected better. If the devs aren't running the subreddit, then they should be aware that the guys that do are damaging their brand.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@jrmain commented on GitHub (Mar 12, 2019):

For what it's worth, yesterday I posted about the problem in that subreddit as well. No responses as yet.

@jrmain commented on GitHub (Mar 12, 2019): For what it's worth, yesterday I posted about the problem in that subreddit as well. No responses as yet.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@pleg commented on GitHub (Mar 17, 2019):

here is a workaround for this problem. go into the device manager and disable the network interface used for internet. check the task manager for memory usage of qBittorrent: if memory usage does not change the program is hanging. if memory usage changes qBittorrent is saving progress and shutting down. after qBittorrent has vanished from task manager you can enable network again, and safely shut down.

@pleg commented on GitHub (Mar 17, 2019): here is a **workaround** for this problem. go into the _device manager_ and disable the network interface used for internet. check the _task manager_ for memory usage of _qBittorrent_: if memory usage does not change the program is hanging. if memory usage changes _qBittorrent_ is saving progress and shutting down. after _qBittorrent_ has vanished from _task manager_ you can enable network again, and safely shut down.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@Poldraunic-zz commented on GitHub (Jan 12, 2020):

When is this issue going to be addressed? Now qBittorrent prevent even my system (Windows 10) from shutting down. Sometimes, I have try to shutdown system up to 3 times for which I have no patience at all.

@Poldraunic-zz commented on GitHub (Jan 12, 2020): When is this issue going to be addressed? Now qBittorrent prevent even my system (Windows 10) from shutting down. Sometimes, I have try to shutdown system up to 3 times for which I have no patience at all.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@pleg commented on GitHub (Jan 26, 2020):

@Poldraunic have you tried my workaround to disable the network interface? this fixes it for me. but just for me? if you try this and it closes cleanly, and you report back here, it could help finding the problem!

it seems to me the bug is a deadlock somewhere in the network stack, and the way the connection queue is architected. its probably a complex one that is hard to reproduce.

@pleg commented on GitHub (Jan 26, 2020): @Poldraunic have you tried my workaround to **disable the network interface**? this fixes it for me. but just for me? if you try this and it closes cleanly, and you report back here, it could help finding the problem! it seems to me the bug is a deadlock somewhere in the network stack, and the way the connection queue is architected. its probably a complex one that is hard to reproduce.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@Poldraunic-zz commented on GitHub (Jan 27, 2020):

@pleg
Yes, I have tried it and it indeed works, but I don't consider this a viable solution, just an annoying workaround.

I don't think this is a hard issue to reproduce: it happens to me about 8 out of 10 times. Getting to underlying issue, however, might be tricky.

Now that I think about it, I have couple torrents with unreachable trackers. Perhaps issue lies somewhere there? For example, program received shutdown signal and starts announcing last bits of information to trackers. Some of them, however, are down and it gets stuck because of it. @pleg, do you have any torrents with unreachable trackers?

@Poldraunic-zz commented on GitHub (Jan 27, 2020): @pleg Yes, I have tried it and it indeed works, but I don't consider this a viable solution, just an annoying workaround. I don't think this is a hard issue to reproduce: it happens to me about 8 out of 10 times. Getting to underlying issue, however, might be tricky. Now that I think about it, I have couple torrents with unreachable trackers. Perhaps issue lies somewhere there? For example, program received shutdown signal and starts announcing last bits of information to trackers. Some of them, however, are down and it gets stuck because of it. @pleg, do you have any torrents with unreachable trackers?

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@pleg commented on GitHub (Jan 27, 2020):

@Poldraunic
i mean its hard to reproduce for the devs. they need to debug it.

yes, i have a lot of torrents with unreachable trackers.
it could be, that it tries to announce to trackers that it is no longer seeding.
maybe 200 torrents having a bad tracker address plus the retry/timeout limit creates the issue.
it will wait forever on a nonexisting tracker to respond.

@pleg commented on GitHub (Jan 27, 2020): @Poldraunic i mean its hard to reproduce for the devs. they need to debug it. yes, i have a lot of torrents with unreachable trackers. it could be, that it tries to announce to trackers that it is no longer seeding. maybe 200 torrents having a bad tracker address plus the retry/timeout limit creates the issue. it will wait forever on a nonexisting tracker to respond.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@RoadTrain commented on GitHub (Jan 27, 2020):

In cases like this it's usually a good idea to take an application dump right when it's deadlocked.
You can see which threads are waiting and for what exactly (you might need debug symbols though).
Of course if a developer is willing to take a look. And dumps can contain sensitive information, so it's better not to post them in public.
For me this issue stopped reproducing a long time ago so I can't really help.

@RoadTrain commented on GitHub (Jan 27, 2020): In cases like this it's usually a good idea to take an application dump right when it's deadlocked. You can see which threads are waiting and for what exactly (you might need debug symbols though). Of course if a developer is willing to take a look. And dumps can contain sensitive information, so it's better not to post them in public. For me this issue stopped reproducing a long time ago so I can't really help.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Jan 28, 2020):

@ All

Can ye please provide a little more details?

qBittorrent version and Operating System (especially build) e.g. Windows 10 Pro x64 Build 18363.592 (November Update 1909)

Under advanced options
disk cache?
asyncronous i/o threads?
enable OS cache->checked/unchecked?

regarding systems:
amount of ram installed?
spin hard drive or ssd?

@xavier2k6 commented on GitHub (Jan 28, 2020): @ All Can ye please provide a little more details? qBittorrent version and Operating System (especially build) e.g. Windows 10 Pro x64 Build **_18363.592_** (November Update 1909) **Under advanced options** disk cache? asyncronous i/o threads? enable OS cache->checked/unchecked? regarding systems: amount of ram installed? spin hard drive or ssd?

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@Poldraunic-zz commented on GitHub (Jan 28, 2020):

Software:

Windows 10 Pro N, version 1903, build 18362.592
qBittorrent v4.1.5 (64bit)
- disk cache: 64 MiB
- async i/o threads: 4
- enable OS cache: checked

Hardware:

16 GB RAM installed
system is installed on SSD; qBittorrent is installed on HDD; torrent contents are on 2 different HDDs.

@Poldraunic-zz commented on GitHub (Jan 28, 2020): Software: - Windows 10 Pro N, version 1903, build 18362.592 - qBittorrent v4.1.5 (64bit) - disk cache: 64 MiB - async i/o threads: 4 - enable OS cache: checked Hardware: - 16 GB RAM installed - system is installed on SSD; qBittorrent is installed on HDD; torrent contents are on 2 different HDDs.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Jan 28, 2020):

@Poldraunic please update qbittorrent to latest 4.1 branch (4.1.9.1) or actual latest 4.2 branch

qBittorrent changelog

4.2.x
ATTENTION: This 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 previous versions. If you run it and then downgrade to a previous qBittorrent version then your torrents will probably start rechecking.

4.2.1
ATTENTION: There's a slight change in the way network interfaces are configured. If you have a specific network interface/local address set in the Advanced Settings, go and make sure that your settings have stayed the same. The extra setting for Listen on IPv6 address has been removed.

@xavier2k6 commented on GitHub (Jan 28, 2020): @Poldraunic please update qbittorrent to latest 4.1 branch (4.1.9.1) or actual latest 4.2 branch [qBittorrent changelog](https://www.qbittorrent.org/news.php) **4.2.x** ATTENTION: This 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 previous versions. If you run it and then downgrade to a previous qBittorrent version then your torrents will probably start rechecking. **4.2.1** ATTENTION: There's a slight change in the way network interfaces are configured. If you have a specific network interface/local address set in the Advanced Settings, go and make sure that your settings have stayed the same. The extra setting for Listen on IPv6 address has been removed.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Jan 28, 2020):

To all users in this thread: perform a clean install of qbittorrent.

This means:

Uninstall.
Backup the BT_backup folder in %AppData% (this is what contains the data about your added torrents)
Delete all qbittorrent config files in %AppData%
Install the latest version, leave all settings as default
Add some test torrents, see if the problem persists.
If there is no problem, incrementally change each setting to your preferred setup, making sure to restart qBittorrent between settings changes. If at any point the problem reappears, we now know it must be from some setting or some settings combination.
If there still is no problem, close qBittorrent, restore your BT_backup folder and see if the shutdown problem still happens. If the problem appears at this stage, we now know the issue must be with a specific torrent/tracker.
Post your findings here.

@Tri125 The qBittorrent subreddit is not official. If you keep saying this issue happens to you but fail to provide steps to reproduce it, or maybe stacktraces, etc, expect people to assume there is a problem with your setup, not with qBittorrent. The ban was probably due to the fact that qBittorrent is sometimes subject to FUD campaigns (stalled meme, etc), and a user providing no useful data becomes indistinguishable from a troll, thus the mods must have decided to err on the side of caution.

ignoring a bug for an entire year is something but silencing users trying to bring attention to the issue is crossing the line

Nobody is ignoring anything. There is nothing to be ignored since no actionable data has been provided. At this point what is known is that there might be a problem with network interfaces on Windows. Until it is proven that the problem is on qBittorrent's side, nothing can be done. It could just be the case that some users have bad network drivers on Windows, a boost bug, a libtorrent bug, etc. Nobody is out to get you and this is not a big conspiracy being silenced.

I expected better.

Yeah. I also expected better from certain users. That they can for once provide a quality issue report about these sorts of problems, with dumps/stacktraces with symbols, proper profiling data, etc, just like contributors/devs have asked for numerous times instead of complaining about how "x bug has existed for y years!!!". But alas, here we are.

@FranciscoPombal commented on GitHub (Jan 28, 2020): To all users in this thread: perform a clean install of qbittorrent. This means: 1. Uninstall. 2. Backup the `BT_backup` folder in %AppData% (this is what contains the data about your added torrents) 3. Delete all qbittorrent config files in %AppData% 4. Install the latest version, leave all settings as default 5. Add some test torrents, see if the problem persists. 6. If there is no problem, incrementally change each setting to your preferred setup, making sure to restart qBittorrent between settings changes. If at any point the problem reappears, we now know it must be from some setting or some settings combination. 7. If there still is no problem, close qBittorrent, restore your `BT_backup` folder and see if the shutdown problem still happens. If the problem appears at this stage, we now know the issue must be with a specific torrent/tracker. 8. Post your findings here. @Tri125 The qBittorrent subreddit is not official. If you keep saying this issue happens to you but fail to provide steps to reproduce it, or maybe stacktraces, etc, expect people to assume there is a problem with _your_ setup, not with qBittorrent. The ban was probably due to the fact that qBittorrent is sometimes subject to FUD campaigns (stalled meme, etc), and a user providing no useful data becomes indistinguishable from a troll, thus the mods must have decided to err on the side of caution. > ignoring a bug for an entire year is something but silencing users trying to bring attention to the issue is crossing the line Nobody is ignoring anything. There is nothing to be ignored since no actionable data has been provided. At this point what is known is that there might be a problem with network interfaces on Windows. Until it is proven that the problem is on qBittorrent's side, nothing can be done. It could just be the case that some users have bad network drivers on Windows, a boost bug, a libtorrent bug, etc. Nobody is out to get you and this is not a big conspiracy being silenced. > I expected better. Yeah. I also expected better from certain users. That they can for once provide a quality issue report about these sorts of problems, with dumps/stacktraces with symbols, proper profiling data, etc, just like contributors/devs have asked for numerous times instead of complaining about how "x bug has existed for y years!!!". But alas, here we are.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@Poldraunic-zz commented on GitHub (Feb 16, 2020):

Updated to a latest version a couple of weeks ago and so far it seem to have resolved shutdown issue.

@Poldraunic-zz commented on GitHub (Feb 16, 2020): Updated to a latest version a couple of weeks ago and so far it seem to have resolved shutdown issue.

deekerman commented

2026-02-21 19:06:13 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Feb 19, 2020):

Closing as duplicate of https://github.com/qbittorrent/qBittorrent/issues/5097

@FranciscoPombal commented on GitHub (Feb 19, 2020): Closing as duplicate of https://github.com/qbittorrent/qBittorrent/issues/5097

Rows
Columns

qBittorent still not shutting down properly #7661

qBittorrent version and Operating System

If on linux, libtorrent and Qt version

What is the problem

What is the expected behavior

Steps to reproduce

Extra info(if any)