starred/qBittorrent

Fork 0

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

qB stalls when closing #9098

New issue

Closed

opened 2026-02-21 19:59:13 -05:00 by deekerman · 15 comments

deekerman commented

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

Owner

Originally created by @BobHD on GitHub (Sep 7, 2019).

Please provide the following information

qBittorrent version and Operating System

4.1.7 on W7x64

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

It's a long time that with the latest version (I don't remember when it started) that qB stalls, and its process is still visible in the Windows 7 x64 Windows Task manager when you close it, either by File->Exit or by Alt-F4.
I always have to end the process in the Windows Task manager, or use taskkill.
That's annoying enough that I dropped on my desktop a .bat file with:

TASKKILL /F /IM qbittorrent.exe /T

to do it more easily.

What is the expected behavior

The process dies wen you quit

Steps to reproduce

File->Ext or Alt-F4

Extra info(if any)

(type here)

Originally created by @BobHD on GitHub (Sep 7, 2019). **Please provide the following information** ### qBittorrent version and Operating System 4.1.7 on W7x64 ### If on linux, libtorrent-rasterbar and Qt version (type here) ### What is the problem It's a long time that with the latest version (I don't remember when it started) that qB stalls, and its process is still visible in the Windows 7 x64 Windows Task manager when you close it, either by File->Exit or by Alt-F4. I always have to end the process in the Windows Task manager, or use taskkill. That's annoying enough that I dropped on my desktop a .bat file with: TASKKILL /F /IM qbittorrent.exe /T to do it more easily. ### What is the expected behavior The process dies wen you quit ### Steps to reproduce File->Ext or Alt-F4 ### Extra info(if any) (type here)

deekerman

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

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-21 19:59:20 -05:00

Author

Owner

@The5kull commented on GitHub (Sep 9, 2019):

I noticed that the 4.2 alpha version has the same problem on W10. I can remember that this happened sometime ago in the v3 range also.

@The5kull commented on GitHub (Sep 9, 2019): I noticed that the 4.2 alpha version has the same problem on W10. I can remember that this happened sometime ago in the v3 range also.

deekerman commented

2026-02-21 19:59:20 -05:00

Author

Owner

@jordaninthesky commented on GitHub (Sep 10, 2019):

It seems to stick around forever until you kill it. The bat file is a good idea.

@jordaninthesky commented on GitHub (Sep 10, 2019): It seems to stick around forever until you kill it. The bat file is a good idea.

deekerman commented

2026-02-21 19:59:20 -05:00

Author

Owner

@BobHD commented on GitHub (Sep 11, 2019):

A good solution to exit it is to use Super F4: https://stefansundin.github.io/superf4/

@BobHD commented on GitHub (Sep 11, 2019): A good solution to exit it is to use Super F4: https://stefansundin.github.io/superf4/

deekerman commented

2026-02-21 19:59:20 -05:00

Author

Owner

@jordaninthesky commented on GitHub (Sep 11, 2019):

That tool seems useful, but personally, I like fewer tasks running in the background even if they aren't high resource consuming. If I start using more applications that have similar issues as qbittorrent, I'll likely use it.

@jordaninthesky commented on GitHub (Sep 11, 2019): That tool seems useful, but personally, I like fewer tasks running in the background even if they aren't high resource consuming. If I start using more applications that have similar issues as qbittorrent, I'll likely use it.

deekerman commented

2026-02-21 19:59:20 -05:00

Author

Owner

@DrBeltway commented on GitHub (Sep 13, 2019):

Also seeing this issue with v4.17.

@DrBeltway commented on GitHub (Sep 13, 2019): Also seeing this issue with v4.17.

deekerman commented

2026-02-21 19:59:20 -05:00

Author

Owner

@wrd2093 commented on GitHub (Nov 22, 2019):

Am using v4.1.9.1 (64-bit) ... Windows 10 Pro ... when I Exit qbittorrent (right-click from icon on system tray) ... it disappears from system tray but a process stays running. When I go to shutdown Windows, it tells me qbitorrent is still running so I go to Task Manager .. it shows 0% .. so I just kill the task. This seems to be with the last few releases?

@wrd2093 commented on GitHub (Nov 22, 2019): Am using v4.1.9.1 (64-bit) ... Windows 10 Pro ... when I Exit qbittorrent (right-click from icon on system tray) ... it disappears from system tray but a process stays running. When I go to shutdown Windows, it tells me qbitorrent is still running so I go to Task Manager .. it shows 0% .. so I just kill the task. This seems to be with the last few releases?

deekerman commented

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

Author

Owner

@xavier2k6 commented on GitHub (Nov 22, 2019):

@wrd2093 is there anything showing in your event viewer logs regarding qbittorrent....it may be silently crashing if it is disappearing from system tray.
windows key+R->type: eventvwr & go to windows logs->application & have a look for "error", "windows error reporting" or "application error" that may have any relation to qbittorrent. You can also use the find option & type qbittorrent

@xavier2k6 commented on GitHub (Nov 22, 2019): @wrd2093 is there anything showing in your event viewer logs regarding qbittorrent....it may be silently crashing if it is disappearing from system tray. windows key+R->type: eventvwr & go to windows logs->application & have a look for "error", "windows error reporting" or "application error" that may have any relation to qbittorrent. You can also use the find option & type qbittorrent

deekerman commented

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

Author

Owner

@p43b1 commented on GitHub (Nov 23, 2019):

I had the same issue in the past; now, I don't know if this is version-correlated but after some mess I decided to install 4.20RC and started to play with the advanced options to see what happened.

I changed "same resume data interval" from 60 minutes to 3 minutes and last two times I closed qbittorrent the process "qbittorrent.exe" disappeared within one minute.

Could someone check and confirm please?

@p43b1 commented on GitHub (Nov 23, 2019): I had the same issue in the past; now, I don't know if this is version-correlated but after some mess I decided to install 4.20RC and started to play with the advanced options to see what happened. I changed "same resume data interval" from 60 minutes to 3 minutes and last two times I closed qbittorrent the process "qbittorrent.exe" disappeared within one minute. Could someone check and confirm please?

deekerman commented

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

Author

Owner

@BobHD commented on GitHub (Nov 23, 2019):

I had the same issue in the past; now, I don't know if this is version-correlated but after some mess I decided to install 4.20RC and started to play with the advanced options to see what happened.

I changed "same resume data interval" from 60 minutes to 3 minutes and last two times I closed qbittorrent the process "qbittorrent.exe" disappeared within one minute.

Could someone check and confirm please?

Unfortunately, I already have this setting at 3mn, and I still get zombie processes. That with W7x64 and QB 4.19.

My solution is to use:

https://stefansundin.github.io/superf4/

I have assigned Alt-Control-F4 to terminate the process, it works like a charm.

But I often get hang ups with new torrent, and I need to kill QB and restart it to make it work.

It's a problem which has been her for YEARS, you'd think that the developers would it make their top priority. QB is by FAR the best torrent client, it's very irritating to see a such annoying bug never corrected.

@BobHD commented on GitHub (Nov 23, 2019): > > > I had the same issue in the past; now, I don't know if this is version-correlated but after some mess I decided to install 4.20RC and started to play with the advanced options to see what happened. > > I changed "same resume data interval" from 60 minutes to 3 minutes and last two times I closed qbittorrent the process "qbittorrent.exe" disappeared within one minute. > > Could someone check and confirm please? Unfortunately, I already have this setting at 3mn, and I still get zombie processes. That with W7x64 and QB 4.19. My solution is to use: https://stefansundin.github.io/superf4/ I have assigned Alt-Control-F4 to terminate the process, it works like a charm. But I often get hang ups with new torrent, and I need to kill QB and restart it to make it work. It's a problem which has been her for YEARS, you'd think that the developers would it make their top priority. QB is by FAR the best torrent client, it's very irritating to see a such annoying bug never corrected.

deekerman commented

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

Author

Owner

@BobHD commented on GitHub (Nov 23, 2019):

I just installed 4.1.9.1, and after 10 tries, the problem did not happen again.

Let's hope...

@BobHD commented on GitHub (Nov 23, 2019): I just installed 4.1.9.1, and after 10 tries, the problem did not happen again. Let's hope...

deekerman commented

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

Author

Owner

@BobHD commented on GitHub (Nov 23, 2019):

Sh..t. I tried on 3 different PCs, I got stalling on the third done, problem's still here.

@BobHD commented on GitHub (Nov 23, 2019): Sh..t. I tried on 3 different PCs, I got stalling on the third done, problem's still here.

deekerman commented

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

Author

Owner

@wrd2093 commented on GitHub (Nov 23, 2019):

@wrd2093 is there anything showing in your event viewer logs regarding qbittorrent....it may be silently crashing if it is disappearing from system tray.
windows key+R->type: eventvwr & go to windows logs->application & have a look for "error", "windows error reporting" or "application error" that may have any relation to qbittorrent. You can also use the find option & type qbittorrent

I searched last few days and couldn't see anything in the logs related to qbittorrent ... but will keep an eye on it. The problem seems intermittent just tried a couple of times now and it was exiting fine so not sure if any pattern as to when problem will occur.

@wrd2093 commented on GitHub (Nov 23, 2019): > @wrd2093 is there anything showing in your event viewer logs regarding qbittorrent....it may be silently crashing if it is disappearing from system tray. > windows key+R->type: eventvwr & go to windows logs->application & have a look for "error", "windows error reporting" or "application error" that may have any relation to qbittorrent. You can also use the find option & type qbittorrent I searched last few days and couldn't see anything in the logs related to qbittorrent ... but will keep an eye on it. The problem seems intermittent just tried a couple of times now and it was exiting fine so not sure if any pattern as to when problem will occur.

deekerman commented

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

Author

Owner

@p43b1 commented on GitHub (Nov 23, 2019):

Unfortunately, I already have this setting at 3mn, and I still get zombie processes. That with W7x64 and QB 4.19.

My solution is to use:

https://stefansundin.github.io/superf4/

I have assigned Alt-Control-F4 to terminate the process, it works like a charm.

But I often get hang ups with new torrent, and I need to kill QB and restart it to make it work.

Doesn't terminating the process create issues with fastresume and thus some torrents start rechecking when qbittorrent.exe starts again next time?

@p43b1 commented on GitHub (Nov 23, 2019): > Unfortunately, I already have this setting at 3mn, and I still get zombie processes. That with W7x64 and QB 4.19. My solution is to use: https://stefansundin.github.io/superf4/ I have assigned Alt-Control-F4 to terminate the process, it works like a charm. But I often get hang ups with new torrent, and I need to kill QB and restart it to make it work. It's a problem which has been her for YEARS, you'd think that the developers would it make their top priority. QB is by FAR the best torrent client, it's very irritating to see a such annoying bug never corrected. Doesn't terminating the process create issues with fastresume and thus some torrents start rechecking when qbittorrent.exe starts again next time?

deekerman commented

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

Author

Owner

@BobHD commented on GitHub (Nov 23, 2019):

I kill QB only when there is not torrent left on the Queue.
Rechecking only happens when there is a torrent downloading, and when a newtorrent stalls.
I can have both: one torrent working, and the the other stalling.

@BobHD commented on GitHub (Nov 23, 2019): I kill QB only when there is not torrent left on the Queue. Rechecking only happens when there is a torrent downloading, and when a newtorrent stalls. I can have both: one torrent working, and the the other stalling.

deekerman commented

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

Author

Owner

@thalieht commented on GitHub (Sep 13, 2020):

Duplicate of #5097

@thalieht commented on GitHub (Sep 13, 2020): Duplicate of #5097