The LimeWire installer will automatically install MRJ 2.2.4, so the MRJ version should not be an issue.

The underlying problem here is that the MRJ is simply not very good. We have also had a great deal of difficulty reproducing these freezes internally.

If people have a chance, they could help us debug this problem by holding down the control key until a console window appears as they open LimeWire. Holding down the control key will cause a popup menu to appear when you click on the LimeWire icon. If you select the "Open" option from the menu and continue to hold down the control key, eventually a console window will appear just before LimeWire starts.

This console window will report any debugging output while you are running LimeWire. It may send you error messages particularly when LimeWire freezes.

If anyone who tries this out could report the errors they find back on this forum, that would be a great help.

Adam,

Thanks for the input. I have tried to use the java console to get more info, but did not see anything there before the software got too slow and I quit.

I can tell you that the response delays do not occur unless I am actually connecting or connected to the network. If I am disconnected, there are no issues.

Also, I would not use the word crash, as the software does not acutally seem to cease functioning. For me, it seems like the CPU is suddenly so loaded with instructions that it is unable to process keyboard or mouse input until it works its way down the stack. You type, nothing happens for a very long time, and then the text slowly appears in the field. I don't think that it is actually generating any java errors, because your commands will eventually be executed if you don't mind waiting a few minutes.

Are there any other system settings I can check? I did upgrade from 9.04 to 9.1 without effect. I increased limewire's memory allocation to 20,000 k; nothing. I am running with virtual memory and the ram disk off.

Hope that helps.

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.

Thanks Adam.

Limiting my connecitons to 2 seems to help a great deal. Still slow at times, but finally useable.

Out of curiosity, if I wanted to try changing the JVM's memory settings, where would I do this?

Thanks again.