How about a new LW beta release?

At least one that fixes the Upload Slot 0Kbs Lockups....

IMHO, LW 2.5.5 Pro is broken to the point where a beta should be rushed somewhat.... I'm been checking around the site for two or three weeks, sort of expecting a fix sooner.... but figured it was time to ask.

I gotta go, and "Kill Uploads" that got stuck since writing this...

Hi John Ream,

I already posted this problem twice: Threads "severe transfer obstructions" from 08-15-2002, and "slowing down uploads until deadlock" from 07-09-2002, but the reaction was only: this is only a "minor bug". And a promise that it will be corrected in the next version.

Now I am looking daily in this forum for a new beta version because this system behaviour is really boring. My reaction now is to lock the hosts which make problems.

Regards: Hermann

the temporary fix would be to put the bandwidth throttling bar to 100% -- meaning no throttling. that _will_ fix the problem, because the code that had the bug was only called from the throttled uploader.

Most of the 0k uploaders are just a minor bug, indeed, since they are shown by the gui, but the LimeWire core already skipped those, so the overall upload abilities are not reduced.

However there are actually two kinds of 0k uploaders, there's the kind I described above, which is just a minor bug, that actually has already been fixed in the development code. The other kind is caused by unresponsive remote clients downloading from you. It will take LimeWire a couple of minutes to identify those and to drop them. - However, there have been rumors about malicious servents that start downloads and reduce the download speed almost to zero, to take away upload slots. I don't know if those rumors are true, but they might be.

The next beta will be out in a few (two or three) weeks, I think. The LimeWire devs are currently working on some major improvements to the gnutella protocol.

i don't think they are true, kieger -- i ran with the most current dev version for many many days, and although i previously had seen _lots_ of 0kb/s uploads, i saw absolutely zero afterwards. what i did see were more accurate descriptions of clients that disconnect, show 0kb/s for awhile, and then eventually show interupted.

Hi (Krieger?),

this is really a good workaround. It's running already some hours in this mode and there are no more troubles.

Thanks so much for this hint, I'm completely happy!
Hermann

no, not krieger, just the guy that found the bug.

You are right: There are still 0k-Uploaders, but more rarely than before I removed the throttle. With this system behaviour I can wait until the next beta release will be out.

I think it is true what krieger wrote: there are 2 kinds of 0k Uploaders.

Regards: Hermann

you're right -- there are two kinds. the kind that you'll see if the throttled is set to 100% (no throttling) is a harmless kind -- this one really is a gui bug, meaning that their inclusion does *not* limit or hurt other uploaders. it's just that for some reason, their 'finished' flag never got set, even though they did finish.

These issues are both fixed in the LimeWire 2.6.0 beta. The bug with throttled uploads has actually been in the code for a long time, so it wasn't new to 2.5.5. The other one (where 0 k/s was displayed) is caused by HTTP HEAD requests. The normal HTTP request is a "GET" request, meaning "give me this files" and here's some other "header" information about me and about the file I'm requesting. A HEAD request asks for just the second part -- just exhange headers with me, the extra infomation, but don't actually give me the file. The HEAD requests would show up in the upload window as having made 0 progress because, of course, no file had been sent. Now, those HEAD requests simply get listed as completed (since they are).

Thanks.