[arnold]

Installed recently Limewire Pro 4.12.3 on my Mac G4 (dual 1.4 GHz) with OSX 10.4.7.
Downloaded some files but had to interrupt and quit LW. Starting LW again it resumed the download but froze after some 20 minutes and only allowed to quit the hard way (command-option-escape). This repeated several times, restarting the Mac did not help not even after running Applejack (check disk, repair permissions and clean user caches).
By accident I started LW and performed a new search. Since then the old downloads are performing OK and no freezes occur.

Has anyone experienced the same behaviour?

arnold

[roger]

Hi arnold,

it would be very helpful for us if you can get a so called "StackTrace" of LimeWire when it freezes. So wait until LimeWire freezes...

1) Start the Console (you find it in /Applications/Utilities)

2) Press the Clear button in the Toolbar

3) Start the Activity Monitor (also in /Applications/Utilities)

4) Select LimeWire from the list of active Programs

5) Select "Send Signal to Process" from the View menu

6) Select "Quit (SIGQUIT)" and press the Send button

You should see some output like the following in the Console now.

Full thread dump Java HotSpot(TM) Client VM (1.5.0_06-64 mixed mode, sharing):

"MessageDispatch" daemon prio=5 tid=0x00532bd0 nid=0x1bff000 in Object.wait() [0xb0e05000..0xb0e05d10]
	at java.lang.Object.wait(Native Method)
	- waiting on <0x2431dc28> (a com.limegroup.gnutella.util.ProcessingQueue)
	at com.limegroup.gnutella.util.ProcessingQueue$Processor.run(ProcessingQueue.java:146)
	- locked <0x2431dc28> (a com.limegroup.gnutella.util.ProcessingQueue)
	at java.lang.Thread.run(Thread.java:613)
	at com.limegroup.gnutella.util.ManagedThread.managedRun(ManagedThread.java:64)
	at com.limegroup.gnutella.util.ManagedThread.run(ManagedThread.java:53)

"DestroyJavaVM" prio=5 tid=0x00501610 nid=0x1801800 waiting on condition [0x00000000..0xb07f97a0]

Select "Save a Copy As..." from Console's File menu, save the output on you Desktop for example and send us the file.

Thanks
Roger

[Lord of the Rings]

From the GForums there's been a certain no. of concerned users that have found LW 4.12.3 pc impossible to use on their systems. But reverting back to 4.10.9 seemed to fix these issues. Probably the usual specific configuration issues ... but thought I might note it anyway.

For more info, search 4.12* on the gforums.

[arnold]

Originally Posted by roger

Hi arnold,

it would be very helpful for us if you can get a so called "StackTrace" of LimeWire when it freezes. So wait until LimeWire freezes...

1) Start the Console (you find it in /Applications/Utilities)

2) Press the Clear button in the Toolbar

3) Start the Activity Monitor (also in /Applications/Utilities)

4) Select LimeWire from the list of active Programs

5) Select "Send Signal to Process" from the View menu

6) Select "Quit (SIGQUIT)" and press the Send button

You should see some output like the following in the Console now.

Full thread dump Java HotSpot(TM) Client VM (1.5.0_06-64 mixed mode, sharing):

"MessageDispatch" daemon prio=5 tid=0x00532bd0 nid=0x1bff000 in Object.wait() [0xb0e05000..0xb0e05d10]
	at java.lang.Object.wait(Native Method)
	- waiting on <0x2431dc28> (a com.limegroup.gnutella.util.ProcessingQueue)
	at com.limegroup.gnutella.util.ProcessingQueue$Processor.run(ProcessingQueue.java:146)
	- locked <0x2431dc28> (a com.limegroup.gnutella.util.ProcessingQueue)
	at java.lang.Thread.run(Thread.java:613)
	at com.limegroup.gnutella.util.ManagedThread.managedRun(ManagedThread.java:64)
	at com.limegroup.gnutella.util.ManagedThread.run(ManagedThread.java:53)

"DestroyJavaVM" prio=5 tid=0x00501610 nid=0x1801800 waiting on condition [0x00000000..0xb07f97a0]

Select "Save a Copy As..." from Console's File menu, save the output on you Desktop for example and send us the file.

Thanks
Roger

Roger,

Did as you instructed apart from the fact that LW was not in the Active Processes, but in All Processes.

Console log is attached.

Hope this helps,
regards,
arnold

[Sam]

Yup, that's a bug. We'll fix it and release a 4.12.4. Sorry for the troubles.

[domino916]

FWIW, Arnold's issue is not limited to MAC. I have the same issue, as well.

Win XP SP2
Java 5.0_7
AMD 4200 Processor

Both downloaded within this past week. Re downloaded LW to make sure it wasn't a fluke. No software problems with the previous version of LW.

Symptoms for me are that LW freezes and stops moving data. The rest of my programs function normally.

[Sam]

Yup, we know exactly what the problem is, and it's not limited to the Mac. We've fixed it and I think built the new version, we'll release it on Monday, and possibly resignal all 4.12.3 users about it since it's a pretty annoying problem. Sorry again for any troubles.