Limewire 'Unexpectanty Quits" on black MacBook
 

Hello All,

This is my first time posting but I wanted to know if Limewire works on the intel macbooks? I only ask because I download & install but when I try to launch the limewire application, it opens, ask to upgrade (I click 'Later'), close the tip-of-the-day, and then it quits.

I have uninstalled and installed again. I have downloaded from firefox & safari (just to be sure), I have also checked my firwalls and I have none up. What am I doing wrong?

Should work.

What OS X version are you running?

If you also open the OS X Console (in the Applications/Utilities folder), you'll see a more specific error message when LW fails to open

version: 10.5.1

I tried installing it again and here is what the OS X Console stated:
"12/5/07 2:20:17 PM [0x0-0x4e04e].com.limegroup.gnutella[419] Invalid memory access of location 00000000 eip=005b6dd8
12/5/07 2:20:23 PM ReportCrash[420] Formulating crash report for process LimeWire[419]
12/5/07 2:20:25 PM ReportCrash[420] Saved crashreport to /Users/jonquiltashaboyd-mcclure/Library/Logs/CrashReporter/LimeWire_2007-12-05-142017_Macintosh.crash using uid: 501 gid: 501, euid: 501 egid: 501
12/5/07 2:20:23 PM com.apple.launchd[79] ([0x0-0x4e04e].com.limegroup.gnutella[419]) Exited abnormally: Bus error"

But the application says that 'Limewire quit unexpectantly'

Thanks for the useful error message.

"Bus error" and "Invalid memory access of location 00000000" usually mean hardware problems (bad RAM), but I'll need to check with an expert.

I'm not on Leopard yet, so this is a long shot: have you tried adding LimeWire to the allowed connections in the Firewall?

It has options for what sites to allow. Its checked to allow all sites, so would I still have to add it and what name/title/address should I put in?

LW is an application, not a site, so I'm not sure what part of the firewall you need to consider.

I checked with an expert on the error message. It does indeed likely indicate bad RAM, or less likely, a bad install of OS X or Java.

So, looking to the firewall or LW settings won't help the underlying problem