Ok, I've been seeing lots of comments like LimeWire running slow on 10.2.4 no matter how beefy the machine. I have that problem - but magnified to the Nth degree.

I recently updated to LimeWire 2.9.7 and have the OS X 10.2.4 update. On a B&W G3 with 512MB RAM (an no other apps running except Finder), launching LimeWire pegs the CPU at 100% utilization for the entire time LimeWire is running. In this state, its effectively unusable since every click takes over 10 minutes.

I've read through the FAQ's and attempted to delete the /Applications/LimeWire and related files and re-install, but I still have the problem. Has anyone else encountered this? FYI, I was also encountering this with the older version of LimeWire, so I did the update.
I recall a recent Java update for OS X (1.4.1?). Could that be causing the problem??

Thanks for any hints

blue

Hi blue

Been watching my LW CPU usage in process viewer, and it stays 13-26%; sometimes getting up to 50. This is in leaf or Ultrapeer on my G3 700 iBook, 286 RAM, & all the updates on 10.2.4. I'm only sharing 37 files/1.54GB at the moment.

Are you sharing lots of large files that are in high demand? You could try unchecking the connect on startup preference, and only connecting once the hash was completed--the hashing can be consuming. You might be able to isolate whether the hash or the connection attempts were causing the 100%. The hash is supposed to be limited.

The Java update hasn't affected me (we might see LW using 1.4 in the next few days).

2.9.8 is the current version today. I'm guessing you already did the safe boot/permissions fix, so disabling Ultrapeer is all I can suggest for now. poster jannuss might know more.

Two more thoughts--have you tried the install with a newly created admin user? That would tell you if it's a hardware or a software problem. Secondly, are you in an area where you'd be in high demand as an Ultrapeer? (just a thought).

Hi Stief,

I went back and read the Installer logs and rm -rf the directories and files it had installed (including some in the System/Library), then ran the 2.9.8 installer again. This time it acted more normally. Let me see what the process viewer says...
Hmm, yep, about 6% when just open and not searching or downloading. So, it looks like my big problem is fixed.

I still occasionally get "Unexpectedly quit" errors. Is the LimeWire team interested in getting things like the LimeWire.crash.log?

To answer some of your other questions, I don't think I can be an ultra peer, since I'm behind a NAT firewall. Most of the preference settings I just leave at default settings.

If I encounter slowness problems in the future, I'll try some of your suggestions.

Thanks!

blue

Hi blue--Glad to hear it works better so far. I post my crashlogs to the address given on the LW support page, and haven't got any hate mail back . . .

btw, I'm hearing about a 100 file sharing threshold, and so upped my shared folder to >100 files. This seemed to help connections, but the initial hash of 2.4 GB did take 20 minutes even while disconnected. CPU varied from ~40-60%.

The key seems to be keep away from the very popular files to avoid getting swamped with requests, but offer enough rare files to keep you remembered by other Ultrapeers.