LimeWire on Mac OS X 10.5 Leopard
 

I just upgraded my Mac to Leopard (OS X 10.5) and LimeWire no longer works. It launches and brings up the window but then it crashes. I found a LimeWire log file under CrashReporter, it is too big to post the entire file but some of the pertinent information is below. It appears to be a Java problem. I've seen other posts which suggest I download and reinstall Java but Mac does not have Java on their website for Mac OS X 10.5. I tried a version of Java for OS X 10.4 but the installer quit by stating I had the wrong version of the OS installed. Their website says OS X 10.5 comes with an upgraded Java. Well, apparently it does but not one that is LimeWire compatible. I uninstalled LimeWire by moving it from Applications to the Trash and reinstalled it but no luck.

Any ideas? :bangh:

Do other Java apps run? See if Spotlight can find the Apple supplied "java web start" and see if that will run.

same problem
 

I too am having the same problem, launch limewire and it crashes at 56% loaded. I downloaded and reinstalled the latest version to no avail. Any help limewire support people or community? I just re-upped my membership, don't want it to be for nothing.

Here is the error message limewire is kicking out:

LimeWire version 4.14.10 Pro
Java version 1.5.0_13 from Apple Inc.
Mac OS X v. 10.5 on i386
Free/total memory: 106877864/118620160

FATAL ERROR!

java.lang.OutOfMemoryError: Java heap space
at java.lang.AbstractStringBuilder.expandCapacity(Abs tractStringBuilder.java:99)
at java.lang.AbstractStringBuilder.append(AbstractStr ingBuilder.java:575)
at java.lang.StringBuilder.append(StringBuilder.java: 204)
at java.io.UnixFileSystem.resolve(UnixFileSystem.java :93)
at java.io.File.<init>(File.java:284)
at org.limewire.util.FileUtils.getFilesRecursive(File Utils.java:422)
at org.limewire.util.FileUtils.getLengthRecursive(Fil eUtils.java:617)
at com.limegroup.gnutella.gui.library.LibraryTableDat aLine.initialize(LibraryTableDataLine.java:261)
at com.limegroup.gnutella.gui.library.LibraryTableDat aLine.initialize(LibraryTableDataLine.java:46)
at com.limegroup.gnutella.gui.tables.BasicDataLineMod el.getNewDataLine(BasicDataLineModel.java:213)
at com.limegroup.gnutella.gui.tables.BasicDataLineMod el.add(BasicDataLineModel.java:272)
at com.limegroup.gnutella.gui.library.LibraryTableMod el.add(LibraryTableModel.java:63)
at com.limegroup.gnutella.gui.library.LibraryTableMod el.add(LibraryTableModel.java:20)
at com.limegroup.gnutella.gui.tables.AbstractTableMed iator.addUnsorted(AbstractTableMediator.java:507)
at com.limegroup.gnutella.gui.library.LibraryTableMed iator.updateTableFiles(LibraryTableMediator.java:4 39)
at com.limegroup.gnutella.gui.library.LibraryMediator .updateTableFiles(LibraryMediator.java:295)
at com.limegroup.gnutella.gui.library.LibraryTree$Lib raryTreeSelectionListener.valueChanged(LibraryTree .java:654)
at javax.swing.JTree.fireValueChanged(JTree.java:2399 )
at javax.swing.JTree$TreeSelectionRedirector.valueCha nged(JTree.java:2770)
at javax.swing.tree.DefaultTreeSelectionModel.fireVal ueChanged(DefaultTreeSelectionModel.java:629)
at javax.swing.tree.DefaultTreeSelectionModel.notifyP athChange(DefaultTreeSelectionModel.java:1078)
at javax.swing.tree.DefaultTreeSelectionModel.setSele ctionPaths(DefaultTreeSelectionModel.java:287)
at javax.swing.tree.DefaultTreeSelectionModel.setSele ctionPath(DefaultTreeSelectionModel.java:170)
at javax.swing.JTree.setSelectionPath(JTree.java:1174 )
at com.limegroup.gnutella.gui.library.LibraryTree.set InitialSelection(LibraryTree.java:261)
at com.limegroup.gnutella.gui.library.LibraryMediator .<init>(LibraryMediator.java:139)
at com.limegroup.gnutella.gui.library.LibraryMediator .<clinit>(LibraryMediator.java:88)
at com.limegroup.gnutella.gui.MainFrame.<init>(MainFr ame.java:118)
at com.limegroup.gnutella.gui.GUIMediator.<init>(GUIM ediator.java:190)
at com.limegroup.gnutella.gui.GUIMediator.instance(GU IMediator.java:280)
at com.limegroup.gnutella.gui.Initializer.initialize( Initializer.java:301)
at com.limegroup.gnutella.gui.GUILoader.load(GUILoade r.java:58)


-- listing session information --
Current thread: main
Active Threads: 7
Peak Number of Thread: 24
System Load Avg: -1
Objects Pending GC: 0
Free Space In Settings: -1
Free Space In Incomplete: -1
Free Space In Downloads: -1
Heap Memory Usage: init = 19922944(19456K) used = 11742296(11467K) committed = 118620160(115840K) max = 118620160(115840K)
Non-Heap Memory Usage: init = 29523968(28832K) used = 22354712(21830K) committed = 32669696(31904K) max = 121634816(118784K)

-- listing threads --
main: 1
NIODispatcher: 1
AWT-AppKit: 1
Deadlock Detection Thread: 1
AWT-EventQueue-0: 1
AWT-Shutdown: 1
Timer-0: 1


-- listing properties --
DHT_NODE_ID=3F790D88112A8BF59DA9E161DFB17D5518F6ED EB
WINDOW_Y=49
WINDOW_X=150
PORT=29113
TOTAL_CONNECTION_TIME=90857199
RUN_ON_STARTUP=false
ACTIVE_DHT_ROUTETABLE_VERSION=1
FILTER_HASH_QUERIES=true
INSTALLED=true
DISABLE_DHT_NETWORK=false
MAX_ALTS_PER_RESPONSE=11
UI_LIBRARY_TREE_DIVIDER_LOCATION=137
PUBLISH_ALT_LOCS=true
TOTAL_UPTIME=90635
DISABLE_OOB_V2=0.999f
MIN_CONNECT_TIME=4
LAST_SHUTDOWN_TIME=1192651427878
APP_WIDTH=1051
ENABLE_PASSIVE_LEAF_DHT_MODE=true
SESSIONS=69
SHOW_TOTD=false
CLEAR_DOWNLOAD=true
DHT_MODE=PASSIVE_LEAF
ENABLE_PASSIVE_DHT_MODE=true
SHARE_DOWNLOADED_FILES_IN_NON_SHARED_DIRECTORIES=f alse
LAST_ACCEPTABLE_BUG_VERSION=4.13.15
FRACTIONAL_UPTIME=7.779487E-5
CONNECTION_SPEED=1000
LIME_QRP_ENTRIES=lime;wire;limewire;pro;limewirepr o
LAST_EXPIRE_TIME=1193891427695
TOTAL_CONNECTIONS=69
MIN_PASSIVE_LEAF_DHT_INITIAL_UPTIME=1500000
LIME_SEARCH_TERMS=lime;wire;limewire;pro;limewirep ro
RUN_ONCE=true
DHT_BOOTSTRAP_HOSTS=76.8.67.2:6002
APP_HEIGHT=757
CRAWLER_IPS=76.8.67.2;76.8.67.4;64.61.25.172;64.1. ..
LIME_SIGNED_RESPONSE=VTWQABLTOIACAY3PNUXGY2LNMVTXE 33VOAXGO...
EVIL_HOSTS=BearShare 5.2
MAX_DHT_ALT_LOC_QUERY_ATTEMPTS=500
PUBLISH_PUSH_PROXIES=true
MIN_PASSIVE_LEAF_DHT_AVERAGE_UPTIME=360000
MAX_SIM_DOWNLOAD=5
INSPECTOR_IPS=76.8.67.2;76.8.67.4
ENABLE_PUSH_PROXY_QUERIES=true
EVER_ACCEPTED_INCOMING=true
UNSET_FIREWALLED_FROM_CONNECTBACK=true
CLIENT_ID=E5501DE3B6BBC3BBD89832F4B39DE500
HOSTILE_IPS=128.108.*.*;208.109.*.*;64.59.64.0/18...
PLAYER_ENABLED=false
MIN_ACTIVE_DHT_INITIAL_UPTIME=3600000
FLUSH_DELAY_TIME=25
IDLE_CONNECTIONS=2
MIN_ACTIVE_DHT_AVERAGE_UPTIME=1800000

I have heard Apple will be releasing their Java 1.6 for Leopard soonish. They have a beta version of it out now apparently.

In the meantime, there's things you can try. Can't launch LW: Bouncing in Dock (click on link), although some of those things will obviously not apply to the new OSX.

I don't know if Leopard also includes Java 1.4.2 as did Tiger, but if it does, you could jump back to LW 4.12.16 & set Java 1.4 as the java for java apps to use in the meantime. Setting up Java 1.5. I would recommend deleting your LW prefs folder however if you did attempt this. It's found here: /Users/your_username/Library/Preferences/LimeWire
At the bottom of the page of the first link I gave is a sample image showing how to do.

stief - I am able to launch eclipse without problems.

LotR - I tried deleting the preferences. When I launched LW, it went through the wizard to set up my preferences again but once it finished and LW came up it crashed within a few seconds. I'll check the setup disk to see if it has any other version of Java on it. I really hate the way Mac has it set up on their website so only certain versions of Java work on certain versions of the OS. Way too limiting. And, they only have Java for OS up to 10.4, they haven't even bothered posting anything for Leopard. Very aggravating.

Thanks to both of you for your help/suggestions.

I submitted a support request a few days ago and unfortunately have heard nothing. I deleted the prefs and it would load to 62 percent before crashing haha. I installed leopard on two machines and it worked on the one I reformatted, but not the one I upgraded. So, I just ended up reformatting the second machine as well and it works now.

Hi curmudgeon.

I checked with someone who is using 10.5, and all worked well there.
Since Eclipse *may* use different parts of the JVM than LW, I guess it's a inconclusive test of your java install.

Can you get a Console (Applications/Utilities/Console) output of the error messages when LW starts up?

If you can, posting the output at LimeWire Forums is more likely to get the attention of the developers

cheers

Hi fireman.

Thanks for the tip. Once again, looks like a clean install or the Archive and Install methods are less risk than the Update install.

I don't relish the idea of having to do a full install, especially since LW is the only app giving me problems.

I did try reinstalling Java from the install disk but that did not work (but all I did was a reinstall over the existing Java). How do I uninstall Java? I'm wondering if maybe removing all traces of my existing Java and reinstalling it from the Leopard disk would do the trick.

I have to admit I'm a bit of a newbie on Mac. I know applications are deleted by dragging them to the trash bin from the Applications folder but deleting Java from the Applications folder does not seem to uninstall it.

I see Java under /Library, /System, and /System/Frameworks. Maybe it is in even more places. Do I need to delete all of these folders to remove Java? Are there other places?

You need to remove the java receipt files from the receipts folder. Receipts folder sample image. The receipt files are very important to retain normally, however if installation problems, that's the place to remove the specific items. Also see sample image below the one in link.

I have noticed "some" programs need special Leopard updates, but since LW has worked for at least many people, I am guessing the problem is java related. Particularly looking at the above report.

You can also try deleting the LW prefs folder "if" there is one. See bottom of the link page.

BTW how much spare disk space do you have on your system drive?
Which model computer are you using, cpu speed, how much ram, etc.?

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