LW 4.12.3 frozen solid
 

G4, dual 1Ghz processors, 1.5GB RAM. 15Mb broadband connection.

Unfortunately, there is more than one variable here....

I was using OSX 10.4.6 and LW 4.10.9 Pro with no problems.... meaning that selected downloads would continue on uninterrupted for hours or days if/when necessary (obviously, I don't sleep the machine).

In the last dew days, I updated both to OSX 10.4.7 and LW 4.12.3 and since then, I keep finding LW frozen in place, connections frozen, downloads frozen, and impossible to kill (except with kill -9 or Force Quit, etc.

I'm thinking the problem is with LW 4.12.3, since I backed up to 10.4.7 and it doesn't seem to be freezing.

Anyone else seeing this or similar behavior?

I'd like be able to depend on LW, but this is scary.
/d

Hi dcliml

I've only run 4.12.3 for two sessions (18 hrs and 37 hrs) on an iBook, and didn't notice any freezing, even after updating to 10.4.7

If you know how to do a stack trace, or can look at the Console logs, maybe there will be a hint there.

I don't have the iTunes support checked in the LW prefs: perhaps that might be a spot to check.

Mine is doing exactly the same - running powerbook g4 1.33 ghz, 768 ram, 10mb connection osx 10.4.7, LW 4.12.3

its so frustrating! I only bought pro last week and now i cant leave it longer than a couple of hours without it freezing!

hi oliesharp

Can you help get more info about the freezing?

One of the known problems with java and OS X is that the display becomes unresponsive if the OS X Virtual Memory get too high. Could you open the Activity Monitor in the OS X Utilities folder and look at the Virtual Memory size for LimeWire the next time this happens? If the VMem is over 1 GB, that might explain the freezing.

More info is also available from LimeWire's Preferences->Bug Report, where you can click on the button to generate a sample bug report. This will give lots of info about the LW settings. If the button doesn't work because the GUI is frozen (mouse arrow becomes a spinning beachball), sometimes waiting five minutes allows the mouse to work again.