4.1.5 Freezing Windows 10 #8340

Author

Owner

@Havoc0083 commented on GitHub (Jan 30, 2019):

I am also having the same issue and will also sometimes blue screen my system and saying that it is a memory issue but this only happens when using torrents

@Havoc0083 commented on GitHub (Jan 30, 2019): I am also having the same issue and will also sometimes blue screen my system and saying that it is a memory issue but this only happens when using torrents

deekerman commented

Author

Owner

@7Super7 commented on GitHub (Jan 30, 2019):

Same issue, although mine eventually starts working again. But every time I change something in a dropdown (like target directory) it freezes again. Real pain

@7Super7 commented on GitHub (Jan 30, 2019): Same issue, although mine eventually starts working again. But every time I change something in a dropdown (like target directory) it freezes again. Real pain

deekerman commented

Author

Owner

@3xploiton3 commented on GitHub (Feb 3, 2019):

same issue on me,

@3xploiton3 commented on GitHub (Feb 3, 2019): same issue on me,

deekerman commented

Author

Owner

@ghost commented on GitHub (Feb 3, 2019):

Same here...

@ghost commented on GitHub (Feb 3, 2019): Same here...

deekerman commented

Author

Owner

@Yozer commented on GitHub (Feb 9, 2019):

I have the same issue. Windows 10 (for some reason) is suspendending qbittorrent process...
My current workaround is to manually resume it using Resource Monitor.
I'm using laptop but the charger is always plugged in.

@Yozer commented on GitHub (Feb 9, 2019): I have the same issue. Windows 10 (for some reason) is suspendending qbittorrent process... My current workaround is to manually resume it using Resource Monitor. I'm using laptop but the charger is always plugged in.

deekerman commented

Author

Owner

@balu100 commented on GitHub (Feb 13, 2019):

same issue here.

@balu100 commented on GitHub (Feb 13, 2019): same issue here.

deekerman commented

Author

Owner

@abgrac commented on GitHub (May 1, 2019):

Same issue here. W10 + QB 4.1.5. Please find a fix!

@abgrac commented on GitHub (May 1, 2019): Same issue here. W10 + QB 4.1.5. Please find a fix!

deekerman commented

Author

Owner

@thalieht commented on GitHub (May 1, 2019):

Not everyone gets this problem and unless someone finds the cause or points to a possible reason for this then it can't be fixed.

@thalieht commented on GitHub (May 1, 2019): Not everyone gets this problem and unless someone finds the cause or points to a possible reason for this then it can't be fixed.

deekerman commented

Author

Owner

@stdedos commented on GitHub (May 1, 2019):

Please offer us debugging options and/or perf-equivalent methods?
Or, is there a page that describes that and we missed it? 😕

@stdedos commented on GitHub (May 1, 2019): Please offer us debugging options and/or `perf`-equivalent methods? Or, is there a page that describes that and we missed it? 😕

deekerman commented

Author

Owner

@thalieht commented on GitHub (May 1, 2019):

I don't know anything about it so i won't be able to help, should anyone need help, but i found https://github.com/qbittorrent/qBittorrent/issues/5097#issuecomment-208048460

@thalieht commented on GitHub (May 1, 2019): I don't know anything about it so i won't be able to help, should anyone need help, but i found https://github.com/qbittorrent/qBittorrent/issues/5097#issuecomment-208048460

deekerman commented

Author

Owner

@GregariousJB commented on GitHub (Jun 1, 2019):

Same issue. This problem has followed me from Windows 7 to Windows 10, and from ~4.0 to now 4.1.6. A newly-added torrent will get stuck on "Downloading metadata...", and the DHT nodes number at the bottom gets stuck on whatever it was last. It is inevitable. It may take a day, or a week, but it always eventually happens.

Yes, that "never ends" issue above is related, because after qBittorrent inevitably freezes, closing it is impossible. I need to forcibly end its task and restart it to get it working again.

@GregariousJB commented on GitHub (Jun 1, 2019): Same issue. This problem has followed me from Windows 7 to Windows 10, and from ~4.0 to now 4.1.6. A newly-added torrent will get stuck on "Downloading metadata...", and the DHT nodes number at the bottom gets stuck on whatever it was last. It is inevitable. It may take a day, or a week, but it always eventually happens. Yes, that "never ends" issue above is related, because after qBittorrent inevitably freezes, closing it is impossible. I need to forcibly end its task and restart it to get it working again.

deekerman commented

Author

Owner

@fbermel commented on GitHub (Jun 18, 2019):

Hi,

I have the same issue with qbittorrent-4.1.6. It seems to be stuck when loading the torrent's metadata. I've tried to gather WinDbg output like advised in https://github.com/qbittorrent/qBittorrent/issues/10226#issuecomment-488283018 but I have no idea if it's of any worth (I know nothing about development on Win32 platform):

0:000> |* ~* kp

.  0  Id: 1450.13f8 Suspend: 0 Teb: 000000e9`0c3d8000 Unfrozen
 # Child-SP          RetAddr           Call Site
00 000000e9`0cbff7c8 00007ff8`b920a958 ntdll!NtTerminateProcess+0x14
01 000000e9`0cbff7d0 00007ff8`b72fcd8a ntdll!RtlExitUserProcess+0xb8
02 000000e9`0cbff800 00007ff7`a815bd51 KERNEL32!ExitProcessImplementation+0xa
03 000000e9`0cbff830 00007ff7`a815bd07 qbittorrent!exit_or_terminate_process(unsigned int return_code = 0)+0x49 [minkernel\crts\ucrt\src\appcrt\startup\exit.cpp @ 143] 
04 000000e9`0cbff860 00007ff7`a8145b18 qbittorrent!common_exit(int return_code = 0n0, _crt_exit_cleanup_mode cleanup_mode = _crt_exit_full_cleanup (0n0), _crt_exit_return_mode return_mode = _crt_exit_terminate_process (0n0))+0xbb [minkernel\crts\ucrt\src\appcrt\startup\exit.cpp @ 280] 
05 000000e9`0cbff8c0 00007ff8`b72f7bd4 qbittorrent!__scrt_common_main_seh(void)+0x16c [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 290] 
06 000000e9`0cbff900 00007ff8`b920ce71 KERNEL32!BaseThreadInitThunk+0x14
07 000000e9`0cbff930 00000000`00000000 ntdll!RtlUserThreadStart+0x21

@fbermel commented on GitHub (Jun 18, 2019): Hi, I have the same issue with qbittorrent-4.1.6. It seems to be stuck when loading the torrent's metadata. I've tried to gather WinDbg output like advised in https://github.com/qbittorrent/qBittorrent/issues/10226#issuecomment-488283018 but I have no idea if it's of any worth (I know nothing about development on Win32 platform): ``` 0:000> |* ~* kp . 0 Id: 1450.13f8 Suspend: 0 Teb: 000000e9`0c3d8000 Unfrozen # Child-SP RetAddr Call Site 00 000000e9`0cbff7c8 00007ff8`b920a958 ntdll!NtTerminateProcess+0x14 01 000000e9`0cbff7d0 00007ff8`b72fcd8a ntdll!RtlExitUserProcess+0xb8 02 000000e9`0cbff800 00007ff7`a815bd51 KERNEL32!ExitProcessImplementation+0xa 03 000000e9`0cbff830 00007ff7`a815bd07 qbittorrent!exit_or_terminate_process(unsigned int return_code = 0)+0x49 [minkernel\crts\ucrt\src\appcrt\startup\exit.cpp @ 143] 04 000000e9`0cbff860 00007ff7`a8145b18 qbittorrent!common_exit(int return_code = 0n0, _crt_exit_cleanup_mode cleanup_mode = _crt_exit_full_cleanup (0n0), _crt_exit_return_mode return_mode = _crt_exit_terminate_process (0n0))+0xbb [minkernel\crts\ucrt\src\appcrt\startup\exit.cpp @ 280] 05 000000e9`0cbff8c0 00007ff8`b72f7bd4 qbittorrent!__scrt_common_main_seh(void)+0x16c [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 290] 06 000000e9`0cbff900 00007ff8`b920ce71 KERNEL32!BaseThreadInitThunk+0x14 07 000000e9`0cbff930 00000000`00000000 ntdll!RtlUserThreadStart+0x21 ```

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Sep 30, 2019):

Try 4.1.8 & report back.

@xavier2k6 commented on GitHub (Sep 30, 2019): Try 4.1.8 & report back.

deekerman commented

Author

Owner

@GregariousJB commented on GitHub (Oct 4, 2019):

Still happening in 4.1.8. Thanks for looking into this, though.

@GregariousJB commented on GitHub (Oct 4, 2019): Still happening in 4.1.8. Thanks for looking into this, though.

deekerman commented

Author

Owner

@ghost commented on GitHub (Oct 4, 2019):

What worked for me: I just uninstalled all security software from my bank I had (Warsaw 2.9.x) and the problem is gone.

@ghost commented on GitHub (Oct 4, 2019): What worked for me: I just uninstalled all security software from my bank I had (Warsaw 2.9.x) and the problem is gone.

deekerman commented

Author

Owner

@GregariousJB commented on GitHub (Oct 4, 2019):

What worked for me: I just uninstalled all security software from my bank I had (Warsaw 2.9.x) and the problem is gone.

I haven't used antivirus for ~5 years now, and this issue has followed me from Windows 7 about 2 years ago. It started with ~v4.0.

@GregariousJB commented on GitHub (Oct 4, 2019): > What worked for me: I just uninstalled all security software from my bank I had (Warsaw 2.9.x) and the problem is gone. I haven't used antivirus for ~5 years now, and this issue has followed me from Windows 7 about 2 years ago. It started with ~v4.0.

deekerman commented

Author

Owner

@vikdb commented on GitHub (Oct 26, 2019):

same here 4.1.8

@vikdb commented on GitHub (Oct 26, 2019): same here 4.1.8

deekerman commented

Author

Owner

@GregariousJB commented on GitHub (Nov 9, 2019):

Wait a minute. I think I've been following the wrong issue. I don't consistently freeze "every time" I click magnet links. I eventually freeze and clicking on a magnet link just confirms it because then I get stuck on "Downloading metadata...". Then, I need to use task manager to forcibly close the program.

I guess #5097 is more my issue.

So yeah, this doesn't happen for me in 4.1.9.1, Windows 10 x64, and I don't recall it ever happening "every time I click a magnet link". Sorry for the confusion.

@GregariousJB commented on GitHub (Nov 9, 2019): Wait a minute. I think I've been following the wrong issue. I don't consistently freeze "every time" I click magnet links. I *eventually* freeze and clicking on a magnet link just confirms it because then I get stuck on "Downloading metadata...". Then, I need to use task manager to forcibly close the program. I guess #5097 is more my issue. So yeah, this doesn't happen for me in 4.1.9.1, Windows 10 x64, and I don't recall it ever happening "every time I click a magnet link". Sorry for the confusion.

deekerman commented

Author

Owner

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

can those experiencing freezing/not responding on windows 10 please update qbittorrent to 4.1.9.1 & install windows 10 build 1909 (November update) & report back.....build 1909 has helped immensely on my test machines.

@xavier2k6 commented on GitHub (Nov 13, 2019): can those experiencing freezing/not responding on windows 10 please update qbittorrent to 4.1.9.1 & install windows 10 build 1909 (November update) & report back.....build 1909 has helped immensely on my test machines.

deekerman commented

Author

Owner

@steampunk85 commented on GitHub (Nov 19, 2019):

still having the same issue when loading meta data after updating to 4.1.9.1 and WIndows 10. Window will popup for the magnet download but is frozen for around 30 seconds.

@steampunk85 commented on GitHub (Nov 19, 2019): still having the same issue when loading meta data after updating to 4.1.9.1 and WIndows 10. Window will popup for the magnet download but is frozen for around 30 seconds.

deekerman commented

Author

Owner

@gandalfthewhite19890404 commented on GitHub (Nov 25, 2019):

An issue happens not only when adding torrent from URL, even open .torrent causes freezing for a while.

@gandalfthewhite19890404 commented on GitHub (Nov 25, 2019): An issue happens not only when adding torrent from URL, even open .torrent causes freezing for a while.

deekerman commented

Author

Owner

@gsarkardev commented on GitHub (Dec 1, 2019):

@xavier2k6 Even after upgrading to Windows 10 v1909 (build 18363.476) the issue remains the same. Did not notice any improvements.

There's also particular behavior I noticed that didn't catch my eye previously. After qBittorent freezes, its process remains active in Task Manager, but does not seem to consume any resources. At the same time, there's heavy (100%) disk usage from the "System" Windows process which keeps bugging the whole machine down.

Trying to end the qBittorent process produces no results. You have to navigate to "Services", find the misbehaving qBittorent service and end it's process there to fully exit qBittorrent. As soon as this happens, the full disk usage from "System" goes back to normal (about 0.1%) and Windows becomes responsive again.

@gsarkardev commented on GitHub (Dec 1, 2019): @xavier2k6 Even after upgrading to Windows 10 v1909 (build 18363.476) the issue remains the same. Did not notice any improvements. There's also particular behavior I noticed that didn't catch my eye previously. After qBittorent freezes, its process remains active in Task Manager, but does not seem to consume any resources. At the same time, there's heavy (100%) disk usage from the "System" Windows process which keeps bugging the whole machine down. Trying to end the qBittorent process produces no results. You have to navigate to "Services", find the misbehaving qBittorent service and end it's process there to fully exit qBittorrent. As soon as this happens, the full disk usage from "System" goes back to normal (about 0.1%) and Windows becomes responsive again.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Dec 1, 2019):

For all experiencing freezing/not responding!

How many torrents do you have?

What is your "transfer list refresh interval"?
options->advanced->qbittorrent section->transfer list refresh interval

What is your "Asynchronous I/O threads" set to?
options->advanced->libtorrent section->Asynchronous I/O threads

Is "use alternating row colors" checked/unchecked?
options->behavior->transfer list->use alternating row colors

@xavier2k6 commented on GitHub (Dec 1, 2019): For all experiencing freezing/not responding! How many torrents do you have? What is your "transfer list refresh interval"? options->advanced->qbittorrent section->transfer list refresh interval What is your "Asynchronous I/O threads" set to? options->advanced->libtorrent section->Asynchronous I/O threads Is "use alternating row colors" checked/unchecked? options->behavior->transfer list->use alternating row colors

deekerman commented

Author

Owner

@stdedos commented on GitHub (Dec 1, 2019):

How many torrents do you have?

~180
What is your "transfer list refresh rate"?

1500ms
What is your "Asynchronous I/O threads" set to?

4
Is "use alternating row colors" checked/unchecked?

true

@stdedos commented on GitHub (Dec 1, 2019): * > How many torrents do you have? ~180 * > What is your "transfer list refresh rate"? 1500ms * > What is your "Asynchronous I/O threads" set to? 4 * > Is "use alternating row colors" checked/unchecked? `true`

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Dec 1, 2019):

@stdedos apologies - updated my post.

@xavier2k6 commented on GitHub (Dec 1, 2019): @stdedos apologies - updated my post.

deekerman commented

Author

Owner

@gandalfthewhite19890404 commented on GitHub (Dec 5, 2019):

Most noticed when you open list of files in torrents containing many small files.
Also occurs in 4.2.0 too, there none high load of cpu or hdd, just freezing for a while.

@gandalfthewhite19890404 commented on GitHub (Dec 5, 2019): Most noticed when you open list of files in torrents containing many small files. Also occurs in 4.2.0 too, there none high load of cpu or hdd, just freezing for a while.

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Dec 5, 2019):

@gandalfthewhite19890404 see my post 4 places up.

@xavier2k6 commented on GitHub (Dec 5, 2019): @gandalfthewhite19890404 see my post 4 places up.

deekerman commented

Author

Owner

@gandalfthewhite19890404 commented on GitHub (Dec 5, 2019):

Settings:
How many torrents do you have? - 5 (3 are seeding, 2 are in queue for seeding)

What is your "transfer list refresh interval"? - 1500 ms

What is your "Asynchronous I/O threads" set to? - 4

Is "use alternating row colors" checked/unchecked? - checked

@gandalfthewhite19890404 commented on GitHub (Dec 5, 2019): Settings: How many torrents do you have? - 5 (3 are seeding, 2 are in queue for seeding) What is your "transfer list refresh interval"? - 1500 ms What is your "Asynchronous I/O threads" set to? - 4 Is "use alternating row colors" checked/unchecked? - checked

deekerman commented

Author

Owner

@xavier2k6 commented on GitHub (Dec 9, 2019):

Try these settings:

Set your "transfer list refresh interval" ->5000ms (5secs)
options->advanced->qbittorrent section->transfer list refresh interval

Set your "Asynchronous I/O threads" ->64
options->advanced->libtorrent section->Asynchronous I/O threads

uncheck "use alternating row colors"
options->behavior->transfer list->use alternating row colors

@xavier2k6 commented on GitHub (Dec 9, 2019): Try these settings: Set your "transfer list refresh interval" ->5000ms (5secs) options->advanced->qbittorrent section->transfer list refresh interval Set your "Asynchronous I/O threads" ->64 options->advanced->libtorrent section->Asynchronous I/O threads uncheck "use alternating row colors" options->behavior->transfer list->use alternating row colors

deekerman commented

Author

Owner

@gandalfthewhite19890404 commented on GitHub (Dec 9, 2019):

No, it didn't helped.

@gandalfthewhite19890404 commented on GitHub (Dec 9, 2019): No, it didn't helped.

deekerman commented

Author

Owner

@GregariousJB commented on GitHub (Dec 12, 2019):

(Private Internet Access)

After restarting qBit several times and remaining stuck on "Downloading metadata", I changed the qBit connection setting from SOCKS5 to (none), then used the PIA client to "Connect (Auto)", then restarted qBittorrent...

The torrent started downloading immediately.

Maybe this is a PrivateInternetAccess problem getting stuck when using qBittorrent's built-in proxy connection settings? The questions we might want to be asking are, which proxy are you guys using? How are you connecting to it - built-in qBit settings or the downloaded client?

On that note, why is PIA's client working and the built-in qBit settings are not?

@GregariousJB commented on GitHub (Dec 12, 2019): (Private Internet Access) After restarting qBit several times and remaining stuck on "Downloading metadata", I changed the qBit connection setting from SOCKS5 to (none), then used the PIA client to "Connect (Auto)", then restarted qBittorrent... The torrent started downloading immediately. Maybe this is a PrivateInternetAccess problem getting stuck when using qBittorrent's built-in proxy connection settings? The questions we might want to be asking are, which proxy are you guys using? How are you connecting to it - built-in qBit settings or the downloaded client? On that note, why is PIA's client working and the built-in qBit settings are not?

deekerman commented

Author

Owner

@gandalfthewhite19890404 commented on GitHub (Dec 13, 2019):

I am not using any proxies.

@gandalfthewhite19890404 commented on GitHub (Dec 13, 2019): I am not using any proxies.

deekerman commented

Author

Owner

@flickleafy commented on GitHub (Jan 1, 2020):

I have some issue with the lastest version of it freezing. It happened exactly when I updated from 4.1.9 to the 4.2.1.

I opened the logs and the exact moment it freezed was when the log mentioned about re-checking every torrent for integrity. When I do manual checking of files (hashing), it freezes as well.
Looking to the task manager I see it using 100% of 1 cpu core, and HD actitivity as 100% too.

My guess is that there is some problem with multithreading on it, related to hashing files.

@flickleafy commented on GitHub (Jan 1, 2020): I have some issue with the lastest version of it freezing. It happened exactly when I updated from 4.1.9 to the 4.2.1. I opened the logs and the exact moment it freezed was when the log mentioned about re-checking every torrent for integrity. When I do manual checking of files (hashing), it freezes as well. Looking to the task manager I see it using 100% of 1 cpu core, and HD actitivity as 100% too. My guess is that there is some problem with multithreading on it, related to hashing files.

deekerman commented

Author

Owner

@ris-ha commented on GitHub (Mar 4, 2020):

Does anyone happen to be using any programs that use overlays? Like FPS counters from GPU drivers etc.? Disabling ASUS' GPU Tweak fixed it for me.

@ris-ha commented on GitHub (Mar 4, 2020): Does anyone happen to be using any programs that use overlays? Like FPS counters from GPU drivers etc.? Disabling ASUS' GPU Tweak fixed it for me.

deekerman commented

Author

Owner

@tommiph commented on GitHub (Apr 30, 2020):

Does anyone happen to be using any programs that use overlays? Like FPS counters from GPU drivers etc.? Disabling ASUS' GPU Tweak fixed it for me.

THANK YOU! This worked for me too! (on v4.2.5)

@tommiph commented on GitHub (Apr 30, 2020): > Does anyone happen to be using any programs that use overlays? Like FPS counters from GPU drivers etc.? Disabling ASUS' GPU Tweak fixed it for me. THANK YOU! This worked for me too! (on v4.2.5)

deekerman commented