2.4.4 crashes OSX
 

I'm running the latest OSX on an iMac 500MHz machine with 245 Megs of RAM and plenty of disk space.

The problem is I leave LimeWire running overnight, and when I get back to the computer in the morning, LimeWire has either crashed, or the entire machine has hung and I have to do a hardware reset.

This never happens with any of the other programs I leave running for a long time, so the assumption is that LimeWire is malfunctioning in some serious way. :-(

Note that I am a paying LimeWire Pro customer.

Hmm. I also use a 500mHz G3, tho I have 640 RAM. I've never had Limewire do this (I also use 2.4.4). Try leaving it on long term again and see if the same thing happens. It could have been a fluke.

Limewire is a memory hog, however with the dynamically assigned memory in OS X this isn't the problem it was in OS 9.x.

Actually I've tried this almost every night for the past two weeks, and the result is the same-- a hung machine. After LimeWire is running a while in the background, I bring it to the foreground by clicking on the icon in the dock, and then the entire GUI hangs.

LimeWire or underlying problem?
 

Hi czei,

Had it occurred to you that it may not be LimeWire itself that's causing the problem you're experiencing, but an underlying problem with your OS X installation?

The reason I ask is that, in the normal course of events, OS X seems to be fairly stable (i.e., it takes something pretty major to bring it down completely as opposed to merely having an individual app quit). Have you run any diagnostics to check on the 'health' of your filesystem? If not, it might be an idea to do so prior to pursuing the problem LimeWire seems to be causing (it may, after all, simply be bringing to light something otherwise unrelated to LimeWire's performance).

If you want a recommendation on diagnostic software I'd suggest first running 'fsck' (that's the UNIX 'file system check' utility)--see enclosed text file; then, if you have it, Drive 10. I find the combination of these two seems to find/repair most of the problems I've had thus far.

[FYI, I'm successfully--if slowly!--running LimeWire 2.4.4 under OS X 10.1.5 on a PowerBook G3/400/FW with 192mb RAM.]

I would be hesitant to blame the OS. I do a lot of maintenance and have been running OS 10 (.0 through .1.5) successfully. I have had less than 10 crash/kernels/hangups. All but one was LimeWire and/or Java related. It did not kernel, it either crashed the app (disabling ultrapeer fixed that), or after about 24 hours of L W I got a spinning beachball whose only remedy was a force restart on the tower power supply button.

Until I run LimeWire, the system runs G R E A T!!!!!

During LimeWire, it runs like frozen mud, or worse.

Quit LimeWire, performance returns to normal.

But it's Java's fault, as if it mattered.

Here's what has worked for me so far. I find that right around 24 hours of running L W is when I start to have problems. If I go much beyond that, I get the hangup. I have 1 gig of RAM and a 400 MGHZ processor. Just for a reference. I also have about 15 gig of free space on the drive, so free space and memory should not be an issue. I don't know if a dual gig processor would fix it, but it's not an option anyway. Nuff said.

Around the 24 hour mark, I pare down my uploaders from 5 to 0 and then quit the LimeWire program. You will probably find that right afterwards your system will resume its normal characteristics.

Then I go ahead and either get the work done that is important, or if it's a light day, then I restart LimeWire.

It has kept me out of beachball hell to date.

Until somebody fixes the program or the JAVA (a term that is insulting to coffee) we are stuck with workarounds in order to get by.