I have now tried Killing uploads from the uploads queue.

I killed off the uploads in progress first - this resulted in them being removed from the upload queue as expected - but nothing jumped in to take their place despite having around ten "queued" upload requests (There is usually a lot of demand for upload slots - I would expect a free upload slot to be filled instantly).

I then went on to Kill the "queued" uploads. They were removed from my upload queue. - They were eventually (after a minute or so) replaced with other queued items.

I now have 10 queued uploads and one "uploading". However, the one uploading is showing as 0KB/s although the progress bar is now at 1%.

Searching is using up /way/ more processor time than it should (at a rough estimate - an order of magnitude more - err... 10 times more than normal). Oops - not quite true...

A search that returns a total of 152 results uses a normal amount of processor time (a maximum of 50% processor usage (mostly a lot less) for around a minute (normal search time)).

A search that returns a total of 1466 results used up 100% processor for for around 6 minutes.

But (sorry) 1387 results - does go to 100% processor but only for around 20 seconds (A little high - but within spitting distance of normal).

It seems that occassionaly (I can't find a bit of consistency yet) a search takes a lot (a lot) more processor than normal.

Downloads.dat is the same size as reported at the end of my last message.

The progress bars on the upload and download queues seem to be correct - it is just the speed which is stuck.

Mark