Here's something everyone can do to help debugging:

Enable the Console tab, from the combo box select "com.limegroup.gnutella.io.*", from the logging settings select "ALL" and let it run for 10-15 seconds. Then turn logging "OFF", copy/paste the text in the tab and send it to me. Make sure you tell me exactly what was limewire doing when you turn the logging on.

Btw the console tab is a lot of fun to play with, so play with it :)

zab

The only way I can get the information to copy and paste is with the stdout.txt. Is this what you intended or is there another way to copy it from the console page rather than from LimeWireDebug.
I have generated reports both with and without LimeWireDebug running.

If this is how you intended to do it let me know so I can leave instructions for others on how to do it. I have currently broken LimeWire it froze while shutting down after loosing connection and I killed it with task manager.(Big Mistake) but it did show me some of the problems others have posted. I just need to figure out the steps to repair it and we should be able to help others better in the future.

Any way I am hoping to work on it tonight and get back up and send you some of what you asked for soon.

zab

Below is the com.limegroup.gnutella.io.* stooped as LimeWire Lost connection I was DL 6 files fluctuating between 250 and 600KB/s avg about 500KB/s DL from 84 host. Prior to this happening allot of info was flashing across the com.limegroup.gnutella.io.* screen which is probably what you actually need.

Here is another one taken a couple seconds earlier in the loosing connection process DL 5 files around 500KB/s did not see how many host I was DL from.

From Start to lost connection
 

The zip containes from start until I lost connection I had a avg of 7 files DL around 400KB/s around 70 sources running LW connection set at T3 file names 7 at 400 sear. Open files with note pad

7 = 7 files

at 400 = 400KB/s

sear = running search

here's what I think you want...
 

Hello thank you all for your help. Heres what I think you need. Please advise.


la croute

Here is more stack traces...
 

Hello ZAB,

Here is my stack traces from when I was turbo connected all the way to the end. I don't know if it makes a difference but I loged on at 10 last night and I have saved the file at 8:45 this morning.

Hope this helps.

Thank you

la croute

Here is more...
 

another stack traces. this time it is not as long. I believe it did not even connect after it was trying to when I minimized it.

la croute

heres another
 

this one is starting connection which never connected

la croute

Here's the disconnecting stack...
 

here is the disconecting stack

la croute