I would really appreciate an improvement to the 'Kill Upload' option.

I frequently get 0KB/s uploads that stick in my upload queue and prevent anyone else from uploading files (e.g. I have just killed four 0KB/s uploads - they were the only uploads in my queue - I allow up to ten simultaneous uploads).

When I try to remove these from my upload queue it usually takes a few tens to hundreds of clicks to kill the offending uploads.

As far as I can tell, the currently selected file is reset to NULL each time an upload request comes through. At a rough estimate, I get between 5 and 15 requests a second. This doesn't leave me a lot of time to select a file and then click on the 'Kill Upload' button.

Mark

That was me - sorry - didn't realise I wasn't logged in.

Mark

I've got a working implementation that fixes this on my local computer... It's also jam-packed with other neat features (like a visual display of whether or not the host has Chat enabled, a right-click option of killing, displaying the uploading Vendor [LimeWire, BearShare, Gnucleus, etc..], the time remaining in the upload, and it displays the requested filesize & progress instead of displaying the total filesize even if only 10KB was requested).

I'm just running it through a day or so of tests against the network, and then I'll be submitting the patch and letting the developers decide what to do with it.

Unregistered - excellent - I look forward to the improvements in later versions.

Peerless - It isn't any particular uploader - although it might be a particular client. I suspect that trying to block the individual IPs will be a never ending task - the 0KB/s uploaders are a significant proportion of the people who connect (significant being >1% but probably <20%).

Since I sometimes get 0KB/s downloads, I don't know whether the 0KB/s problem is due to the downloader, the uploader or something else (could be several issues).

If LimeWire were to automatically kill off 0KB/s uploads (and downloads) after, say, half an hour it would significantly increase the average upload bandwidth from me, at least.

Mark

There's actually two unrelated problems that could cause 0KB/s uploads in the current LimeWire version (2.5.5).

One is if you're throttling bandwith and the uploader has their HTTP keep-alive enabled (generally for clients that want to upload a portion of a file, then upload another portion, etc..). In this case, the upload gets stuck in a sort of infinite sleeping-loop, and the upload is considered part of the 'active uploads' -- so if you have a max limit of 10, only 9 other uploads will be allowed (until you kill the upload).

The other is uploaders that somehow manage to instantly disconnect, and the core cleans up all the related statistics (meaning it doesn't use an active upload slot), but the GUI still displays it as uploading, because somehow, the uploader's status never changed.

I've found & fixed the first problem (although a temporary workaround would be to disable upload throttling [ie: set 100% allowed] ). I have a workaround for the second problem, but I'm absolutely stymied as to how it could even happen.

Thanks - it's good to know that a solution is on the horizon - I shall wait patiently.

Mark