Using the latest SVN (605984). I have at least 350 torrents seeding and leeching (Where did the torrent counters go?). Most of them using the same tracker, only one is using another tracker. Anyway something is amiss with announcing - sometimes ktorrent reports all torrents to timeout on annoucing. My internet connection is therefore sometimes completely idle as no torrents have peers, but even then the announces time-out. Even announcing manually results in timeouts. No matter which tracker.

As I'm familiar with the most used tracker's source code, it is highly unlikely that it would be its fault. Also the server itself is absolutely responsive and I am not banned.

PS: This might be unrelated but previously when I tried to add a torrent via pasting its URL while all the torrents went down because of this problem, ktorrent reported something about that file protocol dying unexpectedly or something. A similar (or the exact same) error occured with official releases (2.*) on startup when using about the same number of torrents.

EDIT: When I stop all torrents and start them all again - they will all timeout very soon.

J wrote:Using the latest SVN (605984). I have at least 350 torrents seeding and leeching (Where did the torrent counters go?). Most of them using the same tracker, only one is using another tracker. Anyway something is amiss with announcing - sometimes ktorrent reports all torrents to timeout on annoucing. My internet connection is therefore sometimes completely idle as no torrents have peers, but even then the announces time-out. Even announcing manually results in timeouts. No matter which tracker.

As I'm familiar with the most used tracker's source code, it is highly unlikely that it would be its fault. Also the server itself is absolutely responsive and I am not banned.

PS: This might be unrelated but previously when I tried to add a torrent via pasting its URL while all the torrents went down because of this problem, ktorrent reported something about that file protocol dying unexpectedly or something. A similar (or the exact same) error occured with official releases (2.*) on startup when using about the same number of torrents.

EDIT: When I stop all torrents and start them all again - they will all timeout very soon.

What if you start one by one ? Maybe these 350 torrents are a bit much.

George wrote:What if you start one by one ? Maybe these 350 torrents are a bit much.

Stopping all torrents, restarting KTorrent and starting torrents one-by-one helps. However I still need KTorrent to announce all of them from time to time.

Some sort of tracker connection queueing is now built into SVN, right? Before that, ktorrent did announce, but my computer ran out of free memory because of the kio_http processes. But it still did announce even when the computer became almost unresponsive trying to use swap.

EDIT: According to the tracker (after starting all torrents manually again, 5-30 at a time) I'm seeding/downloading about 383 torrents.

I need to drop the timeouts, the KIO http jobs themselves probably have a timeout, so adding our own isn't necessary. And we don't know when each job is started, so our timeout timer is currently started the moment the job is queued.