Shareaza

bump

Probably internal to Shareaza. It queries a tracker for sources, connects to the sources asking them for more sources in the process leading to the expansion and stable phases. If available sources finish seeding or sharing the torrent, Shareaza tries other sources it already knows and if it finds they are no longer available this leads to fast contraction of known sources. If one of the sources it tries connects and gives new sources it goes back to expansion. Just a guess, but it fits the pattern. No idea why Shareaza doesn't get new sources from the tracker. Not really a BitTorrent person, sorry.

Pressed wrong button... I miss delete...