Dead lock of MacOS X triggered by LimeWire?
 

I do see that after letting LimeWire run for several hours that sometimes MacOS X 10.1.3 locks up solid, the mouse moves but nothing reacts to any mouse click. I can not even ping the MacOS X box from my other computers anymore. The last thing I see is that the CPU meter does display a fully loaded CPU, with system load about at 50% and the rest is user load, no idle state. I do share some 600 files (4GB). Does anybody else see this or is my machine special?

I have noticed the same system lock up with Limewire 2.31, OS X 10.1.3, iMac (slot loading.) If I leave Limewire running for several hours, when I return the system is frozen as you described. At first I thought it might be some kind of conflict with OS X's energy saver, but I've noticed this problem only when Limewire is running.

Get the newest version and check whether it's fixed.

I do run the latest software from cvs, so there is no point to upgrade. Also the problem persists since a some months now. And the problem does not happen under Linux, as I am running the same .jar build under Linux as well. I would assume that this is a MacOS X problem triggered somehow by LimeWire.

Maybe a bug in the JRE or a problem with MacOSX...

Total freeze of OS X
 

I have also seen this, with a twist. After having LW up for several hours, and put into the background, I click on the Dock icon and it freezes the whole system!! Bugger!

unix console readout on lockup
 

Howdy,
I am runnin' OSx v10.1.3 and just (again) loaded the most recent version of Limewire. I am still having prolems with the thing lockin'up. It happens whether I am uploading or downloading. I have adjusted all of the prefs to get various configurations. I looked at the console in the OSx system and it gives the followin':

ipcp: up
local IP address: blah blah blah blah
remote IP address: Blah blah blah blah
terminating on signal 15
ipcp: down

That is where the sys locks up (on me anyhow). Maybe you coders can use that and post something for the rest of us.
Regards.
RS sends

Re: unix console readout on lockup
 

I would say this is different from what I was reporting, your problem appears to be an IP address change triggered on either DHCP lease time expire or some networking glitch that removes carrier from the ethernet, also causing MacOS X to think it lost its IP address. In my case I have no such messages, and I do have a static IP address and do not use DHCP.

I get this crash too
 

(see my post in "crashes")

also, an interesting thing is that when I first updated to the latest version I had several days crashfree (and downloaded over 2 gb :)) and then the problem returned. No changes made to my system.

I share 1000 files. (but I was having the problem when I was only sharing 350)

Re: I get this crash too
 

I believe I can run trouble free as long as I have only the three default ultrapeer connections. I do get crashes if LimeWire decides to establish lots of connections to other computers, I do see 40 or more of these occasionally.