Mac OS X 10.2.2
iMac DV slot loading G3@400 512 MB RAM

I was used to run LW since the earlier OS X betas.
I upgraded from 2.7.9 to 2.7.13 and had a very bad surprise

While 2.7.9. opened and ran acceptably fast, 2.7.13 takes about 4 minutes to open, sticking long on "Loading User Interface..." splash screem. After LW eventually opens, it is very very slow e.g. in computing the numebr of shared files - while in the past it was pretty fast to do that.

In addition, it slows down a lot all remaining open applications. Using top, I see an average use of 27% CPU (!!!) and 18% for Window Manager (!!) during the sticky opening screen.

I last updated java together with the OS update.
I think that this is an unacceptable performance drop - 2.7.9 ran smoothly and fast below OS X 10.2.1. Is there any problem with the new 10.2.2 or am I missing something?

Ciao

It's possible that the performance you're seeing is the result of becoming an Ultrapeer. There are almost no differences between 2.7.9 and 2.7.13 (they were primarily installer changes). If you became an Ultrapeer, however, you might see the performance problems you mentioned.

You can tell if you're an Ultrapeer by enabling the connections tab. If it says "Ultrapeer" in the lower left hand corner, then you're an Ultrapeer. You can disable becoming an Ultrapeer in the Tools>>Options window.

Take a look at CptChipJew's post on fixing the CPU bug -- it works.

Now, I keep asking, how do we submit a bug report and get LimeWire to correct its Java code?

It's not a java bug (at least not on LimeWire's side). There's probably a simple workaround by modifying the runLime-script...

You can send the error report to the mailinglists at www.limewire.org.

afisk

I was never set as an Ultrapeer so I'm sure that the problem is not related to that. The problem happened immediately the very first time I launched LW 2.7.13 - before I could even see the user interface - not to talk acting on my preferences.

I followed another workaround, i.e. launching LW directly from the terminal with the command:
java -jar LimeWire.jar

LW launched regularly and worked as fast as 2.7.9 was used to do.

Only drawback: the localized user interface sticked to the basic search window, i.e. selecting e.g. audio did not show the audio specific search fields (title, author, ...).

If this happened with 2.7.13 (and not only to myself, see other posts related to LW 2.7.13 high memory consumptions), this means that 2.7.13 and 2.7.9 were *not* the same.

Anyway, I switched to LW 2.8.0. This latter works fine again without any workaround.