I would welcome any performance improvements - but that isn't the problem (I accept that a popular search may take processor usage to 100% - the problems I'm describing are new in the 2.7.0 and 2.7.1 versions of LimeWire).

There are two serious problems that may or may not be related.

1. If I leave LimeWire running continuously (which I normally do) the speed indicators on the download queue, on the upload queue and i/o on the connections all freeze (between 24 and 48 hours).

2. LimeWire uses more and more processor time - this only becomes obvious after 48 hours or so. This is not fixed by closing down LimeWire and restarting it (it actually gets worse). It is fixed by deleting the download queue (and downloads.dat) completely.

There is something seriously broken that was not broken prior to 2.7.0. I may have forced the problem by stressing LimeWire more than average users... I am not mis-interpreting normal LimeWire behaviour (I know LimeWire can be a resource hog - these problems are over and above that).

LimeWire is currently using 80% to 90% of my processor - I have no connections (set to zero), no uploads (set to zero), no searches (set to 1) and I'm downloading 6 files(maximum of 10). I have an AthlonXP 1500. This is *far* too much processor usage both in absolute terms and in comparison with 2.6.3.

Mark