Hi, i recently installed Limewire version 1.8 for Mac.
I'm running it on an iMac with 65 MB RAM, and I'm having some
serious issues with getting Limewire to run. It wants to hang a lot,
and it is also freezing in odd ways; part of the browser window is
blank (grey) and so on. Any ideas what i might be able to change?
In general, it seems extremely sluggish whereas any other network-
dependent software zips right along.

Have you looked at "About this Computer" under the apple menu? Because I was noticing similar issues today, running version 1.8c under OS 9.2.2, and was astonished to find that Limewire was taking up over 40 megs of RAM, more than my OS!

In the "memory" tab of the program info, it says its minimum size is about 2800K. I set it to a minimum of 3000 and a preferred size of 4000. And yet when I run it - poof, it's huge! Given that, no wonder it runs slowly, doesn't draw the screen properly, etc.

I can't imagine that this isn't some kind of serious bug. Any program that hogs more memory than MS Word should be ashamed of itself.

if you can't make use uf LimeWire you should be ashamed of yourself.

Apple don't even give the Extension manager enough RAM. You need to work with RAM!

Give RAM where where you want your computer to achieve things.

Hi,
I've been having the same problem as the two earlier users. My iMac (64MB RAM, OS 9.1) opens Limewire, but immediately thereafter seems to bog down in memory allotment issues. As stated previously, the RAM used by Limewire (displayed under About This Computer) is huge. Despite the disparaging remarks of a previous response, there seems to be little I can do... changing Limewire's own RAM specification seems inneffective. Interestingly, I HAD NO SUCH PROBLEM USING MAC OS 8.6. I know because I've only recently upgraded. If anyone has discovered what to do, I'd sure appreciate knowing.

Your computer needs more RAM

I have 85 MB RAM alocated to LimeWire - it never crashes. It's simple stuff - app's ship knowing that there is not enough RAM on machines like yours to run then.

RAM is so cheap now, 0.5 of a GIG for under £100 - look at the cost benefit - as it stands you are tring to a make a princess out of a monkey.

No hard feelings - go shopping

andy145

Come on! Face it!
This baby eats too much memory. It's beyond users' tolerance level. Running for several minutes takes it up to 75 MB, and things have gone worse since the latest upgrade. AND, Don't tell me to increase my RAM. I'll buy the full version of LW when this memory problem's solved.

In all fairness, this LW rocks the world. So I'm counting on you guys in developing business!

hi all
A couple of weeks ago my limewire started to freeze upon startup and I couldnt figure out why. After doing all of the usual utilities and fixes I trashed and uninstalled the old limewire (17c or something like that) and upgraded to PRO. Well, its doing the same thing with pro. After a little more looking I found that when the limewire application was running it was using more than 36 megs of ram. My system runs at 30 megs so as you can see my iMac completely grinds to a halt until I can free it up by doing a force-quit on limewire. So I go to the limewire info folder and see that the memory for the program is set for the suggested size (2048K) but it still opens and uses up all available ram again freezing my iMac. does anyone have any suggestions? I have been corresponding with a limewire tech who has been very nice, but not much help. BTW I am running system 9.0.2 on an iMac DV with a cable modem.
As of today, 2/24, I tried it again and the application doesn't complete launching before just disappearing. this is with unstalling everything limewire off of my mac and doing a fresh reinstall from scratch.
What the heck is going on? What was changed??
Kaos
Kaosprods@yahoo.com

This is definitely a strange one. A couple of versions ago (somewhere around 2.0) I had trouble installing an upgrade. Since I already had Mac Runtime for Java 2.2.5 I went to the second download page and snagged the smaller version without the MRJ. As soon as I installed it I started experiencing obvious memory-related problems. Being a longtime Mac user I immediately cranked up the RAM allocation, but this does not solve this problem. On another thread someone suggested allocating 70MB of RAM, but that is ridiculous. Hell I can get the whole MS Office 2001 running fine with less than that! Not to mention that the problem here seems to be that the application is ignoring whatever RAM settings you have anyway. We used to call these rogue apps and I certainly will not miss them when I finally switch to OS-X.

BTW I'm running Limewire on a Powerbook G3 333 with 192MB RAM under OS 9.2. Despite reinstalling MRJ 2.2.5 twice and three successive versions of Limewire (including the current one), the app launches using about 40MB of RAM and just keeps gobbling it up till it crashes ... usually between 75 and 80 MB. If I'm lucky I can squeeze in a download or two before it's game over.

A few versions ago (the one with the different, nicer icon) Limewire was a model Java app ... it had a decent, competitive feature set and was very stable. Until this problem is fixed however, I will continue to use Morpheus under Virtual PC. If it's not fixed by the time Morpheus for Mac is released ... bye bye Limewire.

See! I'm telling you.
Allocating memory, let alone buying more RAM is NOT the solution.

This is what we call a BUG, and a serious one. I dare say LW has NO commercial value until it's fixed!

Besides, the maths don't add up. I've got 128 MB RAM.
My OS takes up 35 MB (9.1 Japanese version), and then
LW takes up apprx. 55 MB.
So, mathematics tells me that I've got 38 MB left.

NOT SO WHEN YOU'RE USING LW!
I'm told I've only 1.7 to 3.5 MB left!! Some kind of maths.

Precise symptom.
1. LW starts up with 35-40 MB.
2. Runs alright for 4-5 mins.
3. Suddenly a rattling noise from my G4/400 (minitower).
4. LW is eating up 55-60 MB (the record was 75 MB).
5. Remaining RAM available is 1.7-3.5 MB.
6. LW goes slow, and eventually slows down beyond my tolerance level.
7. Force shutdown (sometimes unsuccessful)

So, it's bad enough that LW is eating up memories, it's also messing up with the remaining RAM.

Strange developers don't comment on this issue... This thread is not the only one discussing memory problem.

I downloaded the newest version of Limewire while waiting for new RAM to be delivered. I was running 128MB. As soon as I downloaded the new version I began to have problems. I kept alocating more memory to limewire, but finaly ran into a situation where everything would just crash from a lack of RAM. Limewire was pulling between 60 and 90(!!!)MB, so, with the OS pulling 40MB or so, you can see that this is just not going to work for anyone with less the 256MB of RAM.

On a positive note, my upgrade was to 512MB and Limewire works great. I would be interested to hear how it is working with 256MB. Hopefuly the developers can workout the memory issues.