I was running LW 2.4 for a while without problems. I upgraded to 2.5 and used it for a while. Then something went snap. I start LW and it comes up normally and connects. I display the status window and watch the host count come up to about 50 or so and then do three or four searches followed by two or three downloads.

By the time the first download finishes [a long while as I'm still stuck at 56K], LimeWire is hogging the machine for 15-20 sec at a time with no keyboard or mouse response. On top of this, completed downloads no longer clear even thought the preference is checked. Limewire gets so unresponsive that I can't close .... I have to do a force quit. Sometimes, that doesn't even work and I have to reset the Mac

I reloaded 2.5 ... no change
I deleted 2.5 and reloaded 2.4 .... no change.
I've also reloaded MRJ 2.2.5 .... no help.

I'm on a 400MHz G3 with 384MB of RAM and 40GB hard disk. LimeWire has been allocated 64MB of RAM and Virtual Memory is turned off.

Anyone have any ideas???

Put ur bandwidth to 50/50, and decrease memory allocation to 12000K(12 mb) 64 MB is way too much memory allocation causing u to crash. also be honest on ur connection setting(56k modem) and lower the amount of connections on the connections tab, probably 2 is good for u. also dont hurt other users on upload or start upload slots.

OK ... allocated mem to 12MB ... connections to 2 ... for bandwidth, do you mean the slider in > Options > Uploads > Basic??? I set it to 50%.

I'm trying these settings right now. And now, another silly question: If LW is allocated 12MB why does the system show its using 53MB???

Too many posts are throwing the 64MB mem
allocation around. If that's way too much, it
needs to be added to all the FAQs ... as a
matter of fact, I believe the FAQs say to use 64MB!!

From what I've seen you don't need to give LimeWire that much more memory in the info window. It will grab about 40 megs anyway no matter what you set it to. Increasing the memory in the info window just makes the unused buffer for LimeWire larger and after a point it doesn't help at all.

Remember: Limewire is a Java app., which means that Java has to load for LW to work. Think of it as a really lousy PC emulator requiring about 40-50 MB just to open. LW itself does not need vast amounts of memory to work. I have been arguing with people on this forum for a long time about throwing tons of memory at LW as if it were PhotoShop.

Java can become very slow to respond and sometimes not respond at all. LW usually happily goes on running under these circumstances, but you have no way of seeing what you are doing. The suggestions here should help the problem.

Thanks for the tips, people.
They have been very helpful.

My experience has taught me to set app mem to 2.5 times the prefered size. I've had good luck running at 12MB, so I'm going to try the 2.5x rule ... setting it to 5.5MB ... and letting Java do whatever .........

I'm not sure if setting the memory size down or setting connections to 2 did the trick, but now I'm getting connected to hundreds of other hosts instead of a couple dozen.

However, I'm finding LW is *EXTREMEMLY* sensitive to system loads. It flails around and dies if I have my MP3 player running at the same time. So I've had to shut the tunes off to download more tunes. Also just being in the connection window while LW is trying to connect causes it to flail around and not get connected. If I go back to the search window, *BANG* .... I get connected quick to piles of hosts. Finally, just doing two downloads over my 56K link [running around 50K] is enough to cause my connections to go down. I'm at the point where I disconnect once I get two or three downloads going, and then reconnect when I'm ready for more downloads.

i am having the same problems--and i've tried all of these fixes to no avail. i'm on the latest version of limewire--i'm on an imac g3 running 9.2.2., 192 megs of ram

is limewire gone for me forever? it used to work so beautifully... now, i lose my downloads, the whole thing dies and freezes, and i have to force quit... and sometimes this makes the whole machine freeze.

can anybody help?

limewire hashes files after they've finished downloading. this takes up a lot of cpu time. just give it a bit of time and it should finish. large files take longer to hash.

I'm glad (???) to see that I have company!!! Same story here; 2.4 was fine, but grief started with 2.6. Tried all the obvious - reloading LW, MJR and even updated to 9.2.2. Like someone pouring molasses over it!!!
I've also tried playing with the memory but that doesn't help either. Is there no one out there to help us?

Note: I think version 2.6.3 leaks memory as the Mac OS and/or LimeWire grows and grows in memory used until you quit LimeWire, restart, or the computer crashes. I haven't tried it but 2.6.5 should have fixed the memory leak and if not, the beta 2.7 is worth a shot.