Using a G4 also with 1 gig of RAM, I find that the 9.2.2 OS performs much better than the one running on OS 10.1.4 on the same machine.
Is it the Java that makes it run so cr*ppy? Argh, it's awful! In a year and two months of various versions of OS 10 and LimeWire (free and Pro), the ONLY crash I have ever had was while LimeWire was running.
The app itself did not "unexpectedly quit", just everything but the pointer stopped working. Forcing a reboot was the only way out.
Wishlist:

Please fix or abandon Java

Please put the "browse host" feature back

On the Apple boards, I have read good things about Sputnix, but I think it's mainly for mp3 files.

It is given high praise for use with OS 10, because it is a Cocoa application, and contains

NO JAVA!!!!!!!

Decaffenated LimeWire, I suppose.

crash unexpectedly quit - type two
 

I just downloaded limewire pro and downloaded a couple of songs but ever since then it crashes after about 5 minutes of being in use. Nothing else is crashing- just limewire. Any ideas? I'm using a brand new g4 OS 9.22

thanks
Kate

Try increasing the memory allocated to LimeWire to about 80 MB in the "Get Info" window.

The main problem for Mac users appears to be the older Java implementation:

Windows / Linux : JRE 1.4
Mac OSX : JRE 1.3.1
Mac OS 8.x/9.x : MRJ 2.2.5 (=JRE 1.1.8)

this, for example means no mouse-wheel support or Cut & Paste for Mac Users which is supported in JRE 1.4, I believe.

As far as crashes are concerned. Apart from increasing the memory, as Adam suggested, you can try deactivating extensions (OS8/9) as these systems tend to suffer a lot of crashes from extension conflicts especially when you have a lot of 3rd party (non Apple) extensions. I often use the Basic OS option in the Extension Manager which only loads some of Apple's standard extensions and no 3rd party ones. That generally reduces the number of crashes. If that fails, you can try restarting with no extensions at all by holding down the shift key at startup (Limewire should still run).

I am using Mac G4 OS 9.1 128 MB
LimeWire seems to work better (not perfect) when I am running no other applications. NONE! Not only because of conflicts, but because of lack of memory. There are too many problems when running other applications with LimeWire. I don't know if this helps anyone, but that's what I've found. :)

crashing...
 

thanks everybody for your help...

it's hard not to have any other apps open though! too much to do - I did notice when I used control click to get outside the the program and start working on other projects... and I gave it more memory... it helped.

Still trying to run LimeWire Pro 2.4 in OS 10.1.4. Spontaneous combustion (app crashes), drags down rest of system if other apps are running, etc. Other users will relate. This is way too bad. I love this program, but it can be a R O Y A L pain unless you want to run nothing else and just share files. Unfortunately, I have to do other things with my computer as well. For the programmers, here is the latest crash log. I'm MORE than WILLING to help do whatever so you can get it right, but I think canning the Java and rebuilding is a good starting point. Sputnix was able to do that, and it's stable.

Well, if I could paste the log into this pane, I would do that. But it won't go. I'll try to email it to you guys.

My specs again: Mac OS 9.1 128MB 10GB hard drive LimeWire 2.4.3 (downloaded a couple of weeks ago)

I see that LW is now eating up 108+MB of my memory. I have it set to 64MB. My OS uses 40+MB. That's only leaving me with less than 8MB, making LW run (when it runs) very slow. I thought this problem was fixed in the 2.4.x versions. When I TRY to run LimeWire now, it won't even load the main search page sometimes. The frame of the window is there and the pop-up to "upgrade to pro" shows, but then blank. If I click where "File" is supposed to be, it will appear and I can quit the program. But it sure makes it difficult to search for anything ;)

Sometimes it will start up normally and after a few minutes it (computer) will start making noises (like it's working hard at something) and then if I click anywhere in LW such as to check connections or monitor and try to go back to search, the window will not reload. I can click on "File" (it will appear) and I can quit. But this sure is frustrating. I'm sorry to complain about something that I got for free, but if there is another fix out there that I'm not aware of... I did a search of the General Mac Support forums for "Eating Memory" and have read them and tried them all.

If Adam reads this, would it still be helpful to e-mail you my "err.txt" and "out.txt" files to review?

Thanks all.

The err.txt and out.txt files may be helpful. It sounds like you're just running out of memory, but there might be something else going on as well. My e-mail is afisk@limepeer.com .

Thanks!