qBittorrent does not shut down completely #7049

New issue

Closed

opened 2026-02-21 18:45:21 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 18:45:21 -05:00

Owner

Originally created by @cryptobasher on GitHub (Mar 20, 2018).

qBittorrent v. 4.0.4 (32bit)
Arch Linux OS (32bit)

libtorrent-rasterbar 1:1.1.6-1.0
qt4 4.8.7-23
qt5-base 5.10.1-5.0

When I launch qBittorent it starts as usual but when I decide to close/exit it by clicking "exit" it closes but in most cases like 90% the process is still running in the background and I have to run System Monitor to shut it down completely and then I can launch it again. I've been using qBittorent for a while and it never happened before, this issue just started after recent updates a couple of days ago.

Originally created by @cryptobasher on GitHub (Mar 20, 2018). qBittorrent v. 4.0.4 (32bit) Arch Linux OS (32bit) libtorrent-rasterbar 1:1.1.6-1.0 qt4 4.8.7-23 qt5-base 5.10.1-5.0 When I launch qBittorent it starts as usual but when I decide to close/exit it by clicking "exit" it closes but in most cases like 90% the process is still running in the background and I have to run System Monitor to shut it down completely and then I can launch it again. I've been using qBittorent for a while and it never happened before, this issue just started after recent updates a couple of days ago.

deekerman

2026-02-21 18:45:21 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-21 18:45:25 -05:00

Author

Owner

@AsphyxNYC commented on GitHub (Mar 21, 2018):

same issue here Only in Windows 64 Bit

@AsphyxNYC commented on GitHub (Mar 21, 2018): same issue here Only in Windows 64 Bit

deekerman commented

2026-02-21 18:45:26 -05:00

Author

Owner

@nazar-pc commented on GitHub (Mar 22, 2018):

I think this is a duplicate of #1332. Please close this and follow earlier issue (there is a workaround there too).

@nazar-pc commented on GitHub (Mar 22, 2018): I think this is a duplicate of #1332. Please close this and follow earlier issue (there is a workaround there too).

deekerman commented

2026-02-21 18:45:26 -05:00

Author

Owner

@ngosang commented on GitHub (Sep 22, 2018):

Duplicate of #5097 #1332

@ngosang commented on GitHub (Sep 22, 2018): Duplicate of #5097 #1332