Does this happen only after running LimeWire for extended periods of time, or does it occur right away?

It sounds like a memory leak that we are unaware of. We will be moving to using the 1.3 JVM from Sun in a future release (most likely in LimeWire 1.5) that includes a far superior garbage collector which may take care of the problem, but we have not addressed anything in this area for the pending release of LimeWire 1.4.

Any more information that you could give us would be very helpful, however, as this is the first report we have heard regarding this particular problem. Thanks.


------------------
Adam Fisk
Lime Peer Technologies Developer