It reads:

processes:
limewire.exe 97%
system idle 3%

performance:
CPU usage 100%

2.4 Ghz
RAM 512 mb

Java 5.0 update 6

With the latest Limewire running, the computer can barely function. With the previous version, no problem.

What could be the cause of this? Has anyone else reported problems with the latest version?

People have reported it with every version of LimeWire and it is a bad install of Java that has always been the cause of it. You can try Java 6 it is a Beta and see if that helps or not. You can get it at the link below.

http://java.sun.com/javase/6/

__________________










A little common sense goes a long way

Later Grandpa

I tried Java beta version 6 as you suggested, but Limewire would not open with it saying "Java not detected by Limewire". I am back to version 5, but the 100% cpu usage problem persists.

Why should this have started when before there was no problem at all?

I have checked the other forum links, but they are of no avail.

Any other suggestions before I send my money to Kazaa?

I though I'd try the latest 4.12.3 and the latest Java Beta: still 100% cpu usage! As we can see from the forum, this is a widespread problem. What could it possibly be?!

The only thing I can suggest is to try a complete reinstall of Limewire and Java. Delete .limewire folder (it's the preferences folder) your incomplete folder. Uninstall using the uninstall file in your Limewire programfolder (do not use add/remove programs as it may mess up your Limewire). Then do a search for Limewire and delete everything it finds (unless offcourse you have a saved folder for music etc. that you called LImewire...). then press start and run regedit, go to HKEY_LOCAL_MACHINE>Software and delete the limewire folder from there if there is one. Delete Java using add/remove programs. I would recommend that you do a malware sweep of your PC. 10% CPU usage isn't normal when not running any programs.

Then reinstall Java using the link Grandpa posted and then download the latest offline installer for Limewire. Install that and pray.

BTW I have had this problem once myself and I got rid of it somehow through something of the above. Now it's running great. Using 4.10.9Pro (haven't tried to update yet)