Thanks very much for the reply.

I did a little bit of my own testing over the weekend, and I was able to find some interesting results. Unfortunately, there's not a whole lot you as a user (or even me as a programmer) can do about this.

The underlying problem seems to have to do with the Mac "Java Virtualy Machine" not recycling its memory efficiently. I am going to increase the default memory allocation for the next release, but I am not confident that this will improve the situation very much. I do not believe that the user configurable memory settings actually affect the memory allocation to the JVM, but I am not sure on this.

The best that you can probably do is to try to use as little memory as possible within LimeWire. You can do this through techniques such as not running searches that will return thousands of results (using more specific search terms than "B**tles," for example) and pressing the "Stop" button when you have enough results. Killing old search tabs should also free memory. You can also reduce your number of connections in the "Connections" tab to 2. This will not dramatically decrease your search results, and it should improve performance.

Finally, not sharing huge numbers of files should decrease the necessary memory.

As I have mentioned elsewhere, the OSX version of LimeWire should be significantly better. We will also be releasing a new OSX version with LimeWire 1.5 with a much smaller download size and a new look.

Thanks again for your help.