LimeWire 3.5.3 Beta
 

We've just released LimeWire 3.5.3 beta. This version uses Java 1.4 on Mac OS X if it's available, which should improve performance significantly. If you don't have Java 1.4 on your OS X system, we strongly recommend downloading it using software update. LimeWire 3.5.3 also includes several bug fixes over 3.5.2.

As always, the free version is available at:

http://www.limewire.com/english/content/beta.shtml

If you are a pro user, you can download the beta from your pro download page.

Thanks very much for everyone's help!

-LimeWire Team

I get the Lw gui freeze à la Jum's builds. Oh well, I don't blame Lw because I know the GUI implementation of java 1.4 by apple is very corner cutted.... Back to basic 3.4.7 for me. Désolé.

If you happen to have an account on connect.apple.com you can download DP102, the newer preview of the 1.4.1 Apple JVM, that one is much more stable.

Thanks Jeans, I'm trying LW Jum 3.5.3 on DP102 right now. I'll keep you informed how it goes. BTW I hope LW 3.5 release won't use java 1.4 by default at least until mac os x panther 10.3 is out (or an update to java is released), because many users will hate having more problems then they had before (even if java 1.3 is kinda slow).

Bonne soirée,

Got the GUI freeze this morning :( However it is true that DP102 is more stable and has less visual glitches than the current java on 10.2.

Merci quand même

Can you give me some more details as to what happens during the GUI freeze you are experiencing? I have no idea yet what really happens and I would like to investigate further.

We are currently planning on using 1.4 as the default, although we could alter that decision depending on how many issues crop up. What problems in particular do you see as becoming more troublesome for users than 1.3? Any thoughts on this Jens?

Thanks very much.

I can only speek for me and the few people I have talked to in email messages. For me 1.3 is less stable than 1.4 DP102, but without DP 102 I did only run a very short time. For me the 1.3 JVM runs only a few hours up to a day, but no longer than a day without wierd lockups and such ilks. On 1.4 DP102 I can run for several days, up to a week or more. But from rememberings the unpatched 1.4 JVM is not very stable. The DP102 has the one crash remaining that Apple appearently has fixed in the Panther version.

A more pressing question is if the stock 1.4 JVM without the DP102 patch is stable enough for most users, I have to admit I have not tested it. It is also rather difficult to test as the DP102 patch cannot be uninstalled and you need to reinstall OS X from scratch to regain the old version. As I do not have a test system I did not do that as it is too painfull for me.

Is there any way to determine which java you have installed? (IE, the stock software update java, or the DP.)

From the DP102 README:
I would assume a non DP102 machine outputs a different build version, but I have no machine without DP102 to check.

So the output we have on the machine here says build 1.4.1_01-39.

That look old enough to be the released version? I'd just like to make sure we're testing on the generic java 1.4 that is available through software update.

That appears to be the release version. Just the two versions exist, Apple has not issued any other releases of the 1.4 JVM.

FWIW, on my stock G4 iMac running OS 10.26 java -version returns:[If it would help, I'd been planning an erase and install of the G3, which has the current DP version. Let me know and I'll get busy sooner].

Glad to hear LW using the beta forum to taking these careful steps.]

GUI freezing
 

Hi Jen, I get it pretty random it seems, sometimes when I'm playing with the user interface and the rest of the time, I do not interact with it when it happens. For exemple, yesterday I left LW runnning hidden (command-H). This morning when I first saw that the processor was at 100%, I knew the gui froze. When clicking on it the beach ball appeared, and I had to foce quit it from the dock (before quitting it I ran an utility that told me that LW was still uploading full speed fine). When I forced quite it, it crashed. I'd like to show the crash log, but the last crash logged in limewire in the history of the console is 28 august....

Adam: I noted that on my system (iMac g3 512 mg ram) that LW uses nearly two times the amount of physic memory in java 1.4 than with 1.3. (90megs versus 50megs)

I know debugging is hard ans frustrating, but keep rollin'!

Merci de votre patience

I would say if you could run LimeWire on your unmodified box for a few days and report your findings that would help.

Re: GUI freezing
 

From that description I would assume that is with the original 1.4 JVM? I remember seeing something similar, but I did not see it again using DP102.

Hmm, for me 90 megs resident set size (I assume this is what you mean with physical memory) as seen in top is small, I see LimeWire taking around 160 megs.

Wait a sec, I have an idea what could cause the GUI freeze. Do you have the bug reporting option set to always send? If not, set the config to always send.

Currently under OS X LimeWire does produce an out of memory bug every once in a while (actually quite often for me) that does not appear to impact operation much. But if the bug report is not send, it will popup a dialog box asking for what do. These dialog boxes will stack up and lots of them will make the OS X gui so slow as to appear frozen. Check if setting the bugs setting to always send fixes your freeze. if yes it is the stacking dialog problem.

Bonne soirée, Jens, thanks for the replies!

The gui freezes came the same way in regular java 1.4 and DP102 java, minus that with DP102 it seems to take more time to happens. With regular 1.4, it happens within the hour.

On the memory side, this is the resident memory with process viewer and this does not include virtual memory (I don't care about this stat, too depressing... ;) right now near 300megs with freshly started LW basic 3.4.7).

On the always send bug, since the apparition of the option it was checked at always send....

Merci

Stief remembered me that I did recommend one config change in the past: tuning OS X for server use. For this to work you will need to add a line like this to /etc/hostconfig:

SERVER=-YES-

if this is not already in your hostconfig. Upon the next boot OS X will adjust the internal tables for server use, that means more processes, threads and open files.

Hi Jens
Is webserver=-yes- the same as server=yes ? I have the webserver already enabled on my machine.

Merci

No, the SystemTuning startup item only automatically makes SERVER=-YES- if the AFPSERVER or QTSSERVER options are turned on.

Salut Jens,
I did add the line in hostconfig and then I rebooted the machine. Yet the GUI freeze still happened after one hour while swithching tabs in LW. Héhéhé, I hope I'll be the only one in that situation when people upgrade to java 1.4 LW....

Merci

anything I can do to help et voilà? (I owe you for the help with the router). I installed the signed version of LW Pro 3.5.3 Beta on the stock G4 (800mHz iMac/256 Ram) last night, but it's still running now. It's only sharing 182 files . . . Feel free to message/mail me if this is OT

Salut Stief! Well thanks for the offer, but I think this problem has to be specific to my config. I won't reinstall os x to fix the problem (if that's the problem, I doubt it as I don't install any unecessary progs on my 'puter and I don't play with the UNIX guts of the X... much). I'll see if the problem is still there with the upcoming of the panther this fall as I always do a clean install with a new OS.
However I think this is linked to memory as Java 1.4 seems to have a BIG memory leak with LW on my machine.

Bonne fin de semaine à tous

*edit* Félicitations on your 800th post Stief!

Merci. I'm embarrassed to be reminded that 800 proves that quantity does not = quality! I tried turning on all the gui-intensive settings I could find except the audio/video submenus in search results . . .
(Adam/Sam--I can't copy the sample bug report with 3.5.3 on the G4; but can with the 3.5.3jum207 on the G3).

The G4 just had an
Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000001Code[1]: 0x968843f0

and noticed also another crash log called JavaNativeCrash_pid526.log

Unexpected Signal : Bus Error occurred at PC=0x9669186C
Function=[Unknown.]
Library=/System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Libraries/libjvm.dylib

I've put the logs on my public iDisk (stief3 no pw).

Not sure how it happened--I was in the Finder moving a dl from the Shared folder a few minnutes earlier.

I would say a few of those bugs that were fixed under DP102. Not an argument for running on OS X with JVM 1.4 unpatched.

The discussion apears to be moot, as Apple just about now released the latest Java update via software update. So the 1.4.1 JVM with the DP102 fixes will be available to all Mac users.

Great! I'd like to think that we all had something to do with getting the newest Java out there to all Mac users. Heavy-handedly telling LimeWire (perhaps the most-used java app) to use 1.4. :)

Also, FYI, the newest beta (3.5.5) should FINALLY be the last update. We found & fixed the last of the persistent bugs [we think]. The DMG installer now should work for all OSX users, even those on 10.1. Special thanks to Jens-Uwe again for helping us out on the details of what was required for LimeWire.app to be recognized on 10.1.

Thanks everyone for your help with this beta. LimeWire continues to get better and better with your help.

Also, just to ammend that comment... We'd appreciate it if OSX users would test out the DMG installer especially. It's about 1MB smaller, easier to use and takes less time to install. Of course, not many of us here are avid mac users, so sometimes we miss nuances that might otherwise be obvious to the daily mac user. If there's something that would make the DMG installer cleaner, or the ultimate running of LimeWire through it more obvious, please let us know.

Thanks!

Sam, with the new JVM from Software Update, did you try to bring LimeWire in foreground while it is already running by clicking on the dock icon? This produces a console message. I believe that patch fell through the cracks while integrating my patches.

Oops. Maybe 3.5.5 won't be the last release. :)

Is it just a console warning? Does anything terribly bad happen?

It might be worthwhile to just sneak that in 3.6 along with (hopefully) fixes to get magnets working again.

Congrats all on getting such a major fix and improvement.
Jens-Uwe--I can't find out if this update will overwrite the DP. If not, I'll try the official .dmg on the stock G4, and keep to the jums on the G3.

It just issues a stack trace about an AbstractMethodError and continues, so it is minor.

While switching hence forth between the offical build an my build I notice that it asks me again for my preferences regarding bug sending. This is strange.

I tried - it overwrites the DP102 and updates the 1.4.1 JVM to the newest version. I believe now as the update is final there is no reason to keep DP102.

Sure looked good--quick and snappy switching windows, until I tried the dock. I'm stuck with the spinning beachball after looking at the "About" credits, closing that, and then choosing to copy the sample bug message in prefs.
The java update reinstalled the fonts LucidaSans-TypewriterBold--these had been related to a GUI freeze so I'd removed them--but now it's back. I'll have to force-quit LimeWire PRO 3.5.5 beta.

Anyone want the Console entries, or is there anything else I can log before I try force-quit? I can't hide LW or cancel the sample bug message window,but I can drag the windows out of the way and send this message.

Jens-Uwe--you're right again: java -version is the same. Glad the dp doesn't need reformatting for removal.

I would believe that you need to remove the font - it is just a warning. But it might be related to the case that the official installer is missing the one event handler for clicking on the dock icon - I cannot reproduce the about hang on my system even though it displays the same warning.

The new apple update made LW much more stable, I've not had freezes overnight until I tried to click on dock while prefs open this morning (to try)! Weird thing is that the freeze don't take 100% of processor, une première for me.

Bonne chance