Powerbook G4 500Mhz
512Mb RAM
OS 10.2.2
Limewire 2.8.0

Limewire:
peaks at 90% CPU on startup
10%-20% CPU when running idle with stable connections
peaks of 40%-70% CPU when searching
More or less constant at 10% memory (50Mb)

Window Manager peaks appear to be unrelated to Limewire. Mine operates at 2%-7% CPU normally - with or without Limewire running. Running the mouse pointer along the Dock with magnification on, for example, will cause the WM to peak at 60% CPU for a second or so. Many other normal operations (like window or application swapping) will cause similar peaks.

I tried starting Limewire from the Terminal and got similar CPU percentages ('com.limegroup.gnutel' instead of 'Limewire' in the Process Viewer).

I have successfully downloaded and uploaded files with no specific problems apart from the 'Could Not Move To Library' error which occured twice with one specific file (illegal characters?).

Single user, very standard system.

I moved to OS 10.2.1 about a month ago when my ADSL line was installed. My kids immediately downloaded LimeWire (2.7.3) and started sharing files. They've kept the computer so busy that I havedn't had a chance to install much more: Netscape 7, AppleWorks, a few games and utilities.

I moved to 2.7.13 because of the Window Manager bug. Once everything looked OK, I decided to organize all may large .avi and .mpg files into a single folder (2GB) on a separate partition from the systems disk. When I did that everything fell apart.

At the suggestion of some one on this forum, I downloaded 2.8.0Beta in the hopes that it would solve my problems -- it did, and created a rash of new ones.

I repeat what I said earlier, 2.8.0Beta doesn't appear to me to be anywhere near release.

Note: in my problem #2 above, I said that I didn't know when 2.8.0 would allow other applications to run and when not. I think LimeWire is OK if it's the very first application launched after startup. BUT, I suspect that if you launch other applications, exit, and launch again too many times, eventually Window Manager will go crazy.

Reply to Mac Terminator above:

Sure, I've seen Window Manager peak to 60% and more on many occasions with different applications.

The problem that others and I are experiencing is this: with LimeWire running, you launch some other application [even something simple like System Preferences], and Window Manager jumps to 60-90% and stays there. Sometimes it will settle down after 5, 10, or even 15 minutes and sometimes it won't. Totally inconsistant which makes the problem even harder to identify.

Just out of couriosity: how large is your Shared folder and is it physically on your Systems disk?

I think this is very likely related to the use of the external drive, as other users have mentioned similar problems. Can you try changing the shared and save directories to be on the same drive as LimeWire?

I also suspect that this is precisely the cause of the "Could Not Move to Library' bug.

MacTerminator-

I've seen almost precisely the same behavior on my system -- thanks very much. It's good to know I'm not going insane (at least not as far as LimeWire goes =).

The peaks I have never last for more than a couple of seconds

About 7Gb/1300 files and yes it's on the internal drive (single partition).

But I've just done a test setting my LW Saving folder on an External 80Gb Firewire drive and downloading a couple of small files with no errors.

This has always been a big mystery to me. I have three Macs (a dual 1 GHz Quicksilver, A Powerbook G4 500Mhz and a Powerbook G3 233Mhz). I've done tests several times between them: doing a clean installation of the system (usually OS9 as the PBG3 doesn't really have enough muscle for OSX) and installing the same software on two or all three computers. And I've found that even on computers with exactly the same configuration (though obviously not the same model) the same program can work perfectly on one and be practically unuseable with errors on another. Gremlins? You tell me....

Sometimes [temporary] insanity is a natural and very understandable defense-mechanism.

Reply to Adam Fisk above:

My Shared Folder is on the same physical [internal] disk, but on a different partition from the System.

I can't move Shared back to the System parition because there isn't enough room -- the reason I moved it out in the first place.

I've always been of the opinion that separating user data from systems and applications was a healthy thing.

I probably won't have time til late tonight or even tomorrow, but I'll do an eperiment with a small Shared Folder on the systems partition. Back to you then.

Janet

Since installing the beta, some of the aforementioned problems are taken care of (for me). However, I have noticed that every time I leave it alone for an extended time (ie when I am asleep) it quits.
I have my PB's monitor set to go off a after a few minutes of inactivity. I can tell by the file modification times that Limewire always quits just a few minutes after I leave it. Could the monitor going off somehow affect Limwire? Anyone else notice this?

Bruce

PS when I installed the beta, the installer still left the attached file on my desktop, as it did with 2.7.

Attached Files

err.txt (4.3 KB, 226 views)

for Adam Fisk:

I performed the following experiements this morning:

Running LimeWire 2.8.0Beta with Max OS 10.2.1 on a G4/400MHz with 512MB memory:

1. Create a Shared Folder on the Systems disk with two .avi files (160MB total); empty Incomplete Folder:
restart computer
launch PPTP
launch Process View
launch LimeWire (from the application)
--> runs fine. enable incoming searches, do a few searches of my own, start a download. All's well.
launch another applications [AppleWorks]
--> Window Manager climbs to 97%, the colored beach ball spins and spins, the computer is totally frozen. After seven minutes I shut off the power.

2. Repeat the test launching LimeWire from the Terminal Window
--> identical results.

3. & 4. Empty the Shared Folder and delete the Incomplete Folder and repeat tests 1 & 2
--> identical results.

Note: I have an external CD-RW on the FireWire port and a scanner on my SCSI port [I have to switch to System 9 to use it]. The lab tech at my supplier's says that these sometimes cause problems with OS X -- I've yet to experience any.

Janet