You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When qBittorrent notices changes in IP addresses, such change is handled but not reported in the log. Improper or repetitive changes may cause qBittorrent to be unresponsive, or cease any transfer.
Logging events when IP change happened would allow to diagnose such cases of unresponsiveness. If the IP changes are supposed to already be logged, than there is some other action that makes qBittorrent unresponsive unless bound to a single IP address. Anyway
Additionally there is an option "Reannounce to all trackers when IP or port changed", but such changes that trigger reannounces are not reported in the log file. There were reports that qBittorrent is unresponsive in #15822 One of the remedies is specifying qBittorrent to bind to a specific IP address rather than all addresses from all interfaces. However, there is no way to confirm or infirm the effectiveness of this remedy unless the event that causes unresponsiveness is logged.
It seems to me that qBittorrent is consuming all the available network resources (Windows handles of sockets or available ports), and then it starts slowing down because there are no more network resources left (it cannot create new sockets or Windows can not allocate new source ports). However, there is no log entry about this issue, as other programs are also reporting errors of out of network resources during this time. If I exit qBittorrent, the network resources become available again, and other programs stop reporting errors.
The main issue seems to be that qBittorrent is using too many network resources without logging the errors, which is affecting the performance of other programs. It might be a good idea to try limiting the number of connections in qBittorrent's settings or using different network configurations to reduce the load on the system. But in order to do that, there should be means to diagnose that.
Thus, qBittorrent should notify in the log any errors of network resource allocation.
Use case
This is reproducible on qBittorrent 5.0.3 64-bit for Windows (built with libbittorrent 1.2.19.0). To reproduce, you need a Windows computer with multiple network adapters. Unless you specify one IP address from one adapter to bind to, qBittorrent becomes unresponsive in a few seconds after start, as described in #15822 but no action is added to the log file that causes unresponsiveness.
The text was updated successfully, but these errors were encountered:
Suggestion
When qBittorrent notices changes in IP addresses, such change is handled but not reported in the log. Improper or repetitive changes may cause qBittorrent to be unresponsive, or cease any transfer.
Logging events when IP change happened would allow to diagnose such cases of unresponsiveness. If the IP changes are supposed to already be logged, than there is some other action that makes qBittorrent unresponsive unless bound to a single IP address. Anyway
Additionally there is an option "Reannounce to all trackers when IP or port changed", but such changes that trigger reannounces are not reported in the log file. There were reports that qBittorrent is unresponsive in #15822 One of the remedies is specifying qBittorrent to bind to a specific IP address rather than all addresses from all interfaces. However, there is no way to confirm or infirm the effectiveness of this remedy unless the event that causes unresponsiveness is logged.
It seems to me that qBittorrent is consuming all the available network resources (Windows handles of sockets or available ports), and then it starts slowing down because there are no more network resources left (it cannot create new sockets or Windows can not allocate new source ports). However, there is no log entry about this issue, as other programs are also reporting errors of out of network resources during this time. If I exit qBittorrent, the network resources become available again, and other programs stop reporting errors.
The main issue seems to be that qBittorrent is using too many network resources without logging the errors, which is affecting the performance of other programs. It might be a good idea to try limiting the number of connections in qBittorrent's settings or using different network configurations to reduce the load on the system. But in order to do that, there should be means to diagnose that.
Thus, qBittorrent should notify in the log any errors of network resource allocation.
Use case
This is reproducible on qBittorrent 5.0.3 64-bit for Windows (built with libbittorrent 1.2.19.0). To reproduce, you need a Windows computer with multiple network adapters. Unless you specify one IP address from one adapter to bind to, qBittorrent becomes unresponsive in a few seconds after start, as described in #15822 but no action is added to the log file that causes unresponsiveness.
The text was updated successfully, but these errors were encountered: