I came to know of this app very recently and have just been using it for a day or two.

What I have observed is that the app significantly increases download speeds from filehosts that allow multiple connections for the same file. But what I have also observed is that towards the end of a download, there is this runaway effect where the various connection threads close and open in rapid succession as they ask for lesser and lesser sized chunks of the file.

The problem I am facing is that it seems some filehosts do not seem to like this behavior and stop accepting connection requests when the rapid closing and opening of connection intensifies towards the end. Maybe they see it as an attack or a spam, I don't know. But as a result my download fails with only 1-2MB left.

Is there a way to specify only a limited number of these iterations? For example, open and close connections for a thread no more than 3 times OR no more than 2 connection requests per second.

I am going to post the portion of a log for this runaway effect for clarity. In this case, for a successful completion. You can see how the number of connection attempts accelerates rapidly from 21:32:32 onwards.

[Jun 12, 2016 21:26:41] Maximum number of connections is 5
[Jun 12, 2016 21:26:41] Opening connection 1
[Jun 12, 2016 21:26:41] Download speed isn't limited
[Jun 12, 2016 21:26:41] Starting download
[Jun 12, 2016 21:26:41] Opening file on disk...
[Jun 12, 2016 21:26:41] Opening connection 2
[Jun 12, 2016 21:26:42] Opening connection 3
[Jun 12, 2016 21:26:42] Connection 1 receiving data
[Jun 12, 2016 21:26:42] Opening connection 4
[Jun 12, 2016 21:26:42] Connection 2 receiving data
[Jun 12, 2016 21:26:43] Opening connection 5
[Jun 12, 2016 21:26:43] Connection 3 receiving data
[Jun 12, 2016 21:26:43] Connection 4 receiving data
[Jun 12, 2016 21:26:44] Connection 5 receiving data
[Jun 12, 2016 21:30:59] Connection 4 finished receiving data
[Jun 12, 2016 21:30:59] Opening connection 4
[Jun 12, 2016 21:31:00] Connection 4 receiving data
[Jun 12, 2016 21:31:32] Connection 5 finished receiving data
[Jun 12, 2016 21:31:32] Opening connection 5
[Jun 12, 2016 21:31:33] Connection 5 receiving data
[Jun 12, 2016 21:32:12] Connection 4 finished receiving data
[Jun 12, 2016 21:32:12] Opening connection 4
[Jun 12, 2016 21:32:14] Connection 4 receiving data
[Jun 12, 2016 21:32:22] Connection 1 finished receiving data
[Jun 12, 2016 21:32:22] Opening connection 1
[Jun 12, 2016 21:32:23] Connection 1 receiving data
[Jun 12, 2016 21:32:27] Connection 3 finished receiving data
[Jun 12, 2016 21:32:28] Opening connection 3
[Jun 12, 2016 21:32:28] Connection 3 receiving data
[Jun 12, 2016 21:32:32] Connection 5 finished receiving data
[Jun 12, 2016 21:32:32] Opening connection 5
[Jun 12, 2016 21:32:32] Connection 3 finished receiving data
[Jun 12, 2016 21:32:32] Opening connection 3
[Jun 12, 2016 21:32:33] Connection 5 receiving data
[Jun 12, 2016 21:32:33] Connection 3 receiving data
[Jun 12, 2016 21:32:34] Connection 5 finished receiving data
[Jun 12, 2016 21:32:34] Opening connection 5
[Jun 12, 2016 21:32:35] Connection 3 finished receiving data
[Jun 12, 2016 21:32:35] Opening connection 3
[Jun 12, 2016 21:32:35] Connection 5 receiving data
[Jun 12, 2016 21:32:35] Connection 1 finished receiving data
[Jun 12, 2016 21:32:35] Opening connection 1
[Jun 12, 2016 21:32:36] Connection 5 finished receiving data
[Jun 12, 2016 21:32:36] Connection 3 receiving data
[Jun 12, 2016 21:32:36] Connection 3 finished receiving data
[Jun 12, 2016 21:32:36] Connection 1 receiving data
[Jun 12, 2016 21:32:36] Connection 2 finished receiving data
[Jun 12, 2016 21:32:37] Connection 4 finished receiving data
[Jun 12, 2016 21:32:37] Connection 1 finished receiving data
[Jun 12, 2016 21:32:37] Connection 1 closed
[Jun 12, 2016 21:32:37] Connection 2 closed
[Jun 12, 2016 21:32:37] Connection 3 closed
[Jun 12, 2016 21:32:37] Connection 4 closed
[Jun 12, 2016 21:32:37] Connection 5 closed
[Jun 12, 2016 21:32:37] Removing temporary file extension
[Jun 12, 2016 21:32:38] Download complete