Odd pattern of behavior with particular source.
Posted: 10 Nov 2010 18:44Using 2.3.5.1 r8848 to download a batch of files from a 2.3.5.0 push source I saw this:
Three or four files would download immediately. Six or seven more would queue remotely at positions 1, 2, 3 ...
After a while the downloads would complete but the queued ones didn't advance up the queue positions as downloads in front of them finished. They'd all stay put.
After a while longer they'd all change to show No Sources(!).
Re-adding the source via the search result tab results in another three or four downloading promptly and several more queueing up. Wash, rinse, repeat.
It seems there's a bug with queue advancement on push sources. I don't know if it's in the downloading or the uploading Shareaza, and therefore whether it's introduced between 2.3.5.0 and r8848, fixed between 2.3.5.0 and r8848, or present in both. (I suppose it could even be a problem with a hub along the push route instead of either, though I don't see how such a problem would block queue advancement without completely preventing downloading.)
Three or four files would download immediately. Six or seven more would queue remotely at positions 1, 2, 3 ...
After a while the downloads would complete but the queued ones didn't advance up the queue positions as downloads in front of them finished. They'd all stay put.
After a while longer they'd all change to show No Sources(!).
Re-adding the source via the search result tab results in another three or four downloading promptly and several more queueing up. Wash, rinse, repeat.
It seems there's a bug with queue advancement on push sources. I don't know if it's in the downloading or the uploading Shareaza, and therefore whether it's introduced between 2.3.5.0 and r8848, fixed between 2.3.5.0 and r8848, or present in both. (I suppose it could even be a problem with a hub along the push route instead of either, though I don't see how such a problem would block queue advancement without completely preventing downloading.)