LimeWire Quits
 

I was getting those lock-up problems that everyone is talking about but now LimeWire doesn't run long enough for that to even happen.

Now LimeWire "Unexpectedly Quits" after just a few minutes. I am running OS X v. 10.1.4 and LimeWire 2.4.4 I keep getting the error message, "The application LimeWire has unexpectedly quite. All other applications have not been affected."

I used LimeWire for about a week with now problems and then it all started happening. I would get about 90% of an mpeg downloaded and it would unexpectedly quite. That was after being on for a few hours. Now, it quits only after a few minutes! I tried downloading an MP3 and it "Unexpectedly Quit" almost instantly.

I checked the OS X console and it said that it couldn't connect to the "Rulebook Server" . Every time it "Unexpectedly Quits" I check the console and that is what it says.

Anyone know what's going on?

I have seen these unexpected quits as well, but I have seen two flavours. One is with a crash log to console and one without any notice. The one without notice appears to be due to a shortage of file descriptors.

I just stumbled upon a situation that causes LimeWire to crash within minutes repeatedly. I get the occasional unexpected quit like everybody else, but that is random, and sometimes L W will run for hours or days with no problems other than it slows down the OS to a sticky molassesy crawl.

But today when it happened several times I did not realize that I had Classic running. When I quit Classic, the crashes stopped. It's been running normally for over an hour now.

That might be common knowledge, I'm not sure, but if you've got Classic running you might try quitting it to see if it makes any difference.

Today LimeWire quit unexpectedly (again) and Classic wasn't running. In fact nothing else was running. It had been running really well recently but now it decided to quit. I've changed nothing in the preferences or in my OS X setup. Still a mystery....hmmm.

Darn, that's too bad. I thought maybe I had found something that would be helpful until the programmers fix this potentially good application. Since I posted yesterday, I have left L W running overnight with no more problems since quitting Classic, other than the system runs like cr*p due to the java blues I suppose.
Maybe we are due for a major upgrade??????? PLEASE ????????

I just downloaded the new OS update to 10.1.5, and it really performs great. BUT, I can't run LimeWire now for more than a couple of minutes without it crashing. I looked at the console log and I get the same note about the Rulebook Server before it writes to the crash log.
So far, all my other apps run just fine, but my poor LimeWire just can't deal with it.

Is this program going to get better, or is this just as good as it gets? Somebody said it has to do with Apple's version of Java, but whatever the reason, what can we look forward to?

This is a darn shame. I love the program.

Unexpectedly Quits
 

I have the same behavior but it only occurs when running in ultrapeer mode. Startup go's oke. Then clients start to connect to me, and when the leafnode count reaches about 50 or 60 limewire quits.

Can I take it out of ultrapeer mode, and if so, how do you do it? Did that solve your problem?

Ultrapeeper Off
 

Select preferences, then select speed, then uncheck enable ultrapeeper.

Thanks!

I wanted to follow up on the ultrapeer thing. I turned off the ultrapeer in the speed section of the preferences. I am running the latest version of the OS, 10.1.5. I am now at almost 24 hours running LimeWire with no crashes. Upload activity seems just as active as before, so that is the end of the ultrapeer experiment for me. I'm still not sure what useful purpose it serves.

At this point I would find a "browse host" option much more of a worthwhile option than one that causes the program to crash.

Maybe "ultrapeer" should be OFF by default, and then explain to people what it does and allow them to turn it on at their own risk.

Same Problem in 10.1.5 (I think)
 

Since I began to use OS 10.1.5 with Limewire 2.4.4 I cannot maintain a modem connection for more than a few minutes. I've been using OSX and LimeWire together for several months with out much trouble untill now. I'm going to try turning of ultrapeer .

I want to follow up, it has been 10 days since I turned off the ultrapeer capability. My LimeWire has not crashed since then. The LimeWire folks sort of pooh-poohed the idea when I presented it to them, but for me the proof is in the check mark: Disable ultrapeer capability!
Mine is not a modified install of OS 10.1.5. Applications are in their proper place. My drive is partitioned with 9 and 10 separated. I run Disk Warrior, fsck, MacJanitor and XOptimize regularly. I have so far had 3 kernel panics in over a years worth of use. I do not install a lot of junk, just major league apps, well, if you consider Microsoft major league (but I'm not going there, just trying to make a point).
Maybe when 10.2 comes out and Java finally works right one of these days, LimeWire will happily run in the background while we do all the other things we want to do. For now it's still a tradeoff though. Yes, I have eliminated the crashes, but I still have to deal with frozen mollasses like browsing speeds if I surf while sharing. Not good. Anything I can turn off for that?