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.

interesting, I'll try that. I usually set it to 6 ultrapeer connections because search results seem much better when I do. However I'm pretty sure I've had the crash when I did not bump up the connections.

I just had the crash again and checked out a couple things (Limewire was in the background and I saw that it had crashed because it wouldn't come to the foreground when I clicked on it's window)

-- the out.txt and err.txt files were empty, so Limewire didn't log anything
-- once again I was unable to do a ps from a shell
-- tried shutting down, but os x froze as soon as it sent the quit event to Limewire

from now on I'm going to grab the pid after I launch it so next time I can try kill -1 when it's frozen in the background

I have not changed the number of ultrapeer connections - LimeWire does not limit the number of connections that are not ultrapeer (in the user interface anywhere). If I have the many connections, most of them are plain Gnutella ones. I also do have the problem then that most of my bandwith on my DSL line is then eaten up by just the queries.

I just updated to MacOS X 10.1.4 and see if the problem still persists.

problem persists in 10.1.4
 

I can confirm that the problem does still exist in 10.1.4. It hit me last night. I also believed that it was caused by connecting to more than 3 Ultrapeers (I normally use 5 or 6). This problem has been around for at least the last 3 point releases of LimeWire. It is the only program that takes down the whole OS that I use.

My last crash happened when I was connected to only 3 Ultrapeers, was d/l only 2 files, had around 10 queued and was sharing around 500 files. I was moving my mouse to switch applications but never made it. I got the spinning beachball of death and it was all over. This was after running LimeWire for about 10 min. The bug is not caused by any action of the users, it just seems to be a random lock-up of the entire system.

Running:
iBook 500, OS 10.1.4 (also happens in 10.1.3), java 1.3.1 update 1

Oh, and this bug does not occur using Fern so it may be a problem in the GUI code. Also, I am not using hardware accleration in java so maybe this is just a problem for people not uising hardware accleration.

Hi there!

I noticed this crash too! It hurt me for _5_ times today. :(

I am running 10.1.4 and had the latest LimeWire (2.3 I believe, although what was strange, it had buttons to also search for slashdot news and stuff which are gone after I downloaded a news version)

My machine is a iMac DV 400 Slot Loading with 386 MB ram.

When LimeWire locks up I am first not able to bring it to the foreground by clicking on its window or its window icon in the Dock. (Clicking the window Icon in the dock would just do nothing)

However when I try to click the Dock *Icon* of LimeWire then my computer instantly locks up.

So that seems to be the culprit for now.

Next time I get such a crash I will try to force quit LimeWire either through the gui or through the cli.

Could it be that this lockup somehow either crashes the window server (but I can still movie the mouse) or deadlocks it so that it waits for a specific message from limewire?

Thanks a lot,

cu Martin

Sorry, I forgot this: I am now using LimeWire 2.3.4 and it was running for the hole night, so maybe the problem is gone. But I can´t warrantee it.

cu Martin

I did let it run all night and it locked up again under OS X 10.1.4. This time I had a shell window in the foreground with the kill command for the pid of LimeWire already entered, just not pressed return. Everything appeared to be frozen (gui wise), but the shell windows still worked. I did press return and the CPU load meter immediatly returned to normal levels, but the LimeWire window did not disappear from the screen and the gui was still frozen. Typing "ps ax" on the command line did not run to completion either. I just had to reset the machine.

It apears that LimeWire is now frozen again (10.1.4 LW 2.3.4).

Do any of you have an Idea what do to?

My shell seems to be unable to start (theres a ps in the startup script as it seems), Prozess viewer also. :(

cu Martin

Ok, I can contribute some more detail now:

- LimeWire has since now only "deadlocked" my mac if it was in the background, if it was idle (not up or downloading anything) and was running for some time (at least half an hour till now).

- LimeWire did not Crash when it was uploading something. <g>

Whenever it dies, I cant bring it to the foreground by clicking on its window (also when its in the dock).

_But_ I can keep working for as long as I dont try to use any command that tells me something about PID´s on my computer or trys to kill LimeWire in any way.

Whenever I do that my computer just locks up. I cant click anything (but I can use the mouse) and I can´t give it any commands via the keyboard. Also there doesn´t seem to be any kind of timeout that I can wait for.

¿¿ Any Ideas?

Developers are you listening? Or should I/we post this somewhere else?

cu Martin

I was having a serious problem with limewire hanging my machine but it appeared to happen when my system tried to go to sleep. Not just a display sleep but the hard drive sleep. I changed my energy savings options to never have the hard drive sleep and since then I have not had any hangs using limewire.

No, it definitely isn´t the Hardrive sleep. Today LimeWire crashed while using it and my hard drive definitely wasn´t asleep. :(

I also did some tests where I let my harddrive spin down and switched to limeWire then. It worked perfectly and my HardDrive spun up again.

Although I can´t confirm that when LimeWire is in the backround, the Drive spinns down and LimeWire trys to read from it.. it doesn´t lead to a crash.

cu Martin

p.s.: (Sorry for the bad english)

Oh, there might be a correlation between the ammount of connection gnutella has to the Gnutella-net and the time it takes till gnutella comes down.

For me it took at least some hours with 6 connections, but can happen as fast as five minutes with 10 conections.

Do any of you see the same?

cu Martin

I'm having the same problem with the OSX and PC versions of Limewire so I believe it's OS independent. Maybe it's a Java thing.

If this is OS Independant we should definitely get in touch with the developers so that _really_ anoying Bug can be fixed.

I´l try to confirm that thing on a pc too.

One question left: Which Java VM do you use? 1.4 or 1.3.x? That might be verry important.

Thanks a lot,

cu Martin

I am still getting this crash average once per 2 hours
 

at least.

I'd bet it's in the gui -- some kind of event queue overflow or deadlock -- because I can hammer networking on my machine (run iSwipe & eDonkey & several remote shells and launch many http connections) and it doesn't seem to affect the frequency of the crash.

I'm going to try fern.

I have a g4 450dp -- I'm curious to know if this crash is happening more often on dual processor machines.

A bug, that could create hundreds of threads after running LimeWire for a certain time increasing memory and cpu usage drastically, has been fixed in the 2.4.0 code.

Ah, I see. I have let run the latest version from CVS (no version in CVS, so I named it 2.4.0jum1) for all night and it did not lock up. The threads fix appears to have done it.

This is great news!

Sorry to ask this here, but could you send me that working build per e-mail?

All my attempts to build this thing from cvs ended in overflowing error messages. :(

mhaecker at mac.com

Thank you a lot!

cu Martin

The 2.4.0 beta has just been released precompiled on the LimeWire homepage.

http://www.gnutellaforums.com/showth...threadid=10970

I have also done a build that is available at:

http://baghira.han.de/~jum/LimeWire%...jum2%20OSX.dmg

Thank you guys a lot!

Your help to make me go Gnutella again is _much_ apreciated!

:)

Thanks, Martin

Same but with a ttwist
 

the freeze with the moving mouse happened to me as well. i'm runnng 10.2.3 and tried running limewire pro. i install lw pro 2.8.5 with no problem, but it will freeze my comp as it loads the intro window (with the big lime slices). what is to do?

Same but with a ttwist
 

the freeze with the moving mouse happened to me as well. i'm runnng 10.2.3 and tried running limewire pro. i install lw pro 2.8.5 with no problem, but it will freeze my comp as it loads the intro window (with the big lime slices). what is to do?

Well, I am having the same problem in the same way. I am running 10.2.3. LimeWire 2.7.x worked OK but this started when I upgraded to 2.8.5. So, I went back to 2.7.13 and everything was OK until the 2.8.6 upgrade came out...the first time I opened Limewire and it asked during the splash screen if I wanted to upgrade to 2.8.6 (I said no) and then it froze the system after the splash screen disappeared. Interestingly, while frozen, there is very heavy network traffic over my internet connection. Unfortunately, I have only I machine so I can't login from another box and try to see what might really be going on here.

More than a little annoying. Especially since I have been leaving my system running for days at a time as an ultrapeer...if LW wants to know why there's a shortage of ultrapeers, it's because they can't even open the darn program...

Well, I am having the same problem in the same way. I am running 10.2.3. LimeWire 2.7.x worked OK but this started when I upgraded to 2.8.5. So, I went back to 2.7.13 and everything was OK until the 2.8.6 upgrade came out...the first time I opened Limewire and it asked during the splash screen if I wanted to upgrade to 2.8.6 (I said no) and then it froze the system after the splash screen disappeared. Interestingly, while frozen, there is very heavy network traffic over my internet connection. Unfortunately, I have only I machine so I can't login from another box and try to see what might really be going on here.

More than a little annoying. Especially since I have been leaving my system running for days at a time as an ultrapeer...if LW wants to know why there's a shortage of ultrapeers, it's because they can't even open the darn program...

RAM and Processor Cycles
 

I run a
G4 400 640mg ram os 9.2.2 and 10.2.3 (whatever the newest 10 is)

I find it sucks back like 300mb of ram and all of my computer cycles....

This in a file sharing unility does not make sense...

Photoshop does not even do this and its a real program.


Anyone??

chrisgazzola@mac.com

problem solved
 

ok, i have two partitions on my HD. one with OS 9.2.2 and one with 10.2.3.
this is what i did to solve the problem, everything works perfectly now::

1) booted in 9.2.2
2) ran norton disk doctor to scan the 10.2.3 partition
3) got several major problems regarding my system
4) fixed the problems
5) rebooted in 10.2.3
6) installed and ran limewire pro 2.86 PERFECTLY


everything works now.

TRY RUNNIN NORTON DISK DOCTOR
hope your problem will be solved like mine

problems with Norton utilities and Jaguar
 

Foreverpissed,

The majority opinion in the Mac OSX discussion Forum

http://discussions.info.apple.com/

is that Norton Utilities cause more problems than they solve under OS 10.2.3.

Sysmantec, of course, disagrees.

Janet

at this point, i don't really care about the majority of the opinion. it worked great for me. i'm USING limewire with no problems after norton utils fixed the drive problems. so i'm with symantec. go norton.

BETTER SOLUTION
 

download Acquisition 0.72.