It's not RAM that Limewire is hogging, it's CPU cycles.

What I mean by that is the % of processor that's being used by Limewire. Right now, with Limewire in the background with no active searches, it's behaving itself at about 20%. (That's on a Yikes! (PCI graphics) 400 @ 450 Mhz.) As soon as I start 4 or 5 searches that percentage can grow to about 70% or 80% quite easily. That's not entirely Limewire's fault; part of the problem is the Java virtual machine which Limewire runs atop of.

I did have some problems with Limewire a while back where it would basically suck up all available CPU cycles and make my entire machine almost unusable. I haven't had any of those problems with OS X 10.2.2, Java VM 1.3.1, and Limewire 2.7.9.

Hope this helps....