Limewire 2.8.5 in MacOS 10.2.3 = :(

[SleeplessInCanada]

I am running MacOS 10.2.3 with Limewire 2.8.5 (all the latest builds) on my Power Mac G4 500mhz with 384mb ram. I get the same lockups that everyone else is mentioning in this forum. It does not matter how many (or how few) peers I am connecting to, it does not matter how many files I am sharing, it does not matter how many programs I am running alongside limewire, it does not matter if I had just rebooted, IT JUST CRASHES!!! It starts slow, runs slow, and slows down the entire system, as if it were overloading the CPU. For example, it takes two minutes just for the Entourage splash screen to show up while Limewire is running. Limewire is the only program that has ever done this to me. It sucks. Period. I thought that by now the folks who made this program would have heard our cries by now, but alas, even with the latest build, they have done nothing to help us. I am now settling down with Aquisition, and am hereby tossing Limewire out the window. THANKS FOR NOTHING, LIMEWIRE!!!

[trap_jaw]

Apple's Java implementation is extremely buggy. If you have problems with LimeWire run Acquisition from www.xlife.org instead. Acquisition is LimeWire with a native GUI for MacOSX running faster and a little more stable.

Additionally, do not use 2.8.5. Either use 2.8.6 (less buggy) or as trap jaw mentioned, just go with Acquisition until somebody steps up at limewire.
Acquisition runs very stable if you upgrqade your Java to version 1.4.1, which as of now is a preview release available through the Apple Developer Connection, which you can sign up for at no charge.

[trap_jaw]

If you upgrade to Java 1.4.1 for MacOSX, even regular LimeWire should run stable.

With Java 1.3.1, I would get java core crashes, but the app itself would keep running. 1.4.1 eliminated those.
Will 1.4.1 eliminate the many unexpected LimeWire quits also?

[trap_jaw]

Yes. LimeWire only shows this behaviour of unexpected quits on MacOSX using Java 1.3

"Yes. LimeWire only shows this behaviour of unexpected quits on MacOSX using Java 1.3"

Sorry trap_jaw, that is not accurate.

On a whim, I decided to try LimeWire Pro 2.8.6 again, based on your information. I left it running for about 3 hours, and when I returned to the desktop, it had unexpectedly quit, same as before installing Java 1.4.1.

I ran version 0.74 of Acquisition for the better part of a week with NO crashes. NONE!

I was hoping you would be correct, I really was, but Acquisition is far superior in performance. By the way, what has become of your fellow developers? First it was the holidays, now what? Busy preparing for Valentine's Day?

[SleeplessInCanada]

Sorry guys, but regardless of which version of Java I have running, I still get uber-crappy performance while Limewire is running, and I am still going to stick with Aquisition. Thanks anyways!

"Sorry guys, but regardless of which version of Java I have running, I still get uber-crappy performance while Limewire is running, and I am still going to stick with Aquisition. Thanks anyways!"


Yes, I think that is the popular opinion. And still, nothing from "the Team".

[funkymarcus]

LimeWire will currently NOT run within the Java 1.4.1 preview environment on Mac OS X. Even if you've installed 1.4.1, LimeWire will run in the 1.3.1 environment.

With earlier versions of LimeWire and the 1.4.1 Java preview, LimeWire would begin loading in the 1.4.1 environment and fail. With current versions of either, 1.3.1 is used.

Changes in Apple's Java runtime library are at the root of the problem. LimeWire will need some changes if it is to run under 1.4.1 on Mac OS X and provide proper OS integration.

It _is_ possible to run LimeWire under the 1.4.1 preview on Mac OS X by modifying LimeWire slightly to disable all Mac-specific code. This yields a "metal"-themed LimeWire with no OS integration, and as of the current 1.4.1 preview (DP10), is actually _less_ stable than running LimeWire under 1.3.1.

Mark
@version@/10.2.4