This is weird... I was having problems with Tiger and now after upgrading to Leopard, LIMEWIRE starting working just fine again...

I tried to remove Java per your instructions, LotR, and reinstall it from the Leopard disk but to no avail. I then tried to reinstall Leopard via the Archive/Install but again to no avail. I finally broke down and tried the Erase/Install. That finally did the trick but now I have the long, agonizing ordeal of reinstalling my apps.

I'm not sure why I had such troubles but that was not the first time this Mac has had issues. A few months ago, Apple had some update and then all of a sudden several applications stopped launching. They would bounce in the dock a few times and then go away. I had to reinstall Tiger to get it to work again. That was easier though as I just installed Tiger over what was there and did not have to reinstall of my apps like I have to now. I wonder if it is because I have an Intel-based Mac. "The world may never know."

If you test LW after each app is reinstalled, perhaps you'll find the one that "broke" java.

If so, please post back.

Thanks

Just a post of my experience to see if others can use this info. We have a family OS 10.5.5 Mac with with several logins.

One of the logins has no problems with Limeware 4.18.8 (although that user doesn't use Limewire much) and one of the logins experiences the constant crashing (where Limewire was under heavy use). I removed the old Limewire and installed the latest version and the behaviour persisted. My suspicion is related to storing of some Limewire configuration associated with the user that is incompatible with OSX and Limewire.


Here is an excerpt of the log report

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Java information:
Version: Java HotSpot(TM) Client VM (1.5.0_16-133 mixed mode, sharing)
Virtual Machine version: Java HotSpot(TM) Client VM (1.5.0_16-133) for macosx-x86, built on Aug 27 2008 11:00:20 by root with gcc 4.0.1 (Apple Inc. build 5465)

Hi ejsamuel

Your case looks to be somewhat different, since LW does work (at times) in the crashing account. Still, thanks for the interesting info. The key differences between the two accounts are likely to be found in each user's Home/Library/Preferences.

In the crashing account, when LW is closed, moving (or deleting) the Limewire folder out of the Home/Library/Preferences will make LW create fresh new prefs the next time it restarts. Moving the Shared and Incomplete folders from wherever they are stored in that Home account should also help get a fresh new start.

Also, that Library will have other java preferences: .plist files with java in the name, like
java.awt.im.plist
java.plist
JavaApplicationStub.plist

These are also safe to delete.

Limewire Mac OSX Solution
 

Hi everyone,

It seems everyone is having a hard time getting limewire to work.

Here's how to fix it with ease:

Uninstall Limewire 5
Go to Google and search for "Limewire 4.16.7 mac"
Install that one and boom, it works.

The reason limewire 5 doesn't work on Leopard is because Limewire 5 requires Java 1.6+, while this is supposed to be coming through apple's software updates, it isn't for many people, so this will fix it. Trust me, Limewire 5 isn't much nicer, all that changes is basically GUI. :PEACE:

-DZ