Stack Trace 4.10.0 loosing connection

[Grandpa]

I have been having allot of trouble with 4.10.0 loosing connection. I am doing some very heavy DL. I am DL 7 files at 700+MB connecting to between 6 to 10 per file average of 8.5 to 9 per file it will get up to 500KB/s for a short while then start drooping and drop and fluctuate between 200 and 300KB/s.

I have massinger running and the icon in the tray and I will notice it trying to sing in which tells me I have lost connection within a few seconds it will sign in again. In a few minutes it Will be sining in again but this time it will not succeed. I then get the LimeWire does not appear to have a active connection but it will continue to try and sign in. This all happens within 5 to 15 or so min.

The only way to get a connection again is to reboot my computer. After reboot I immediately have a connection. I originally thought it was my problem and it may be I just put a new AMD 64 X2 3800+ in and have been doing some heavy overclocking and tweaking. I checked my RWIN, MTU, TTL, Ping and tested all were set properly for my connection.

I then ran Frostwire and it ran for about a hour before it did it same version. The only difference was it only had 8 connections per file and would max out at around 300KB/s. I have tried it with BS/Lite but I could not get the DL speeds I could only get to 120KB/s and it did not loose connection. I will attempt BS/Lite again and hopefully I can get higher DL speeds so I can rule out my end.

[Grandpa]

Hope these help #2 is just after LW started and was connecting to hosts. #3 was just after messinger started trying to sighn in but LW still showing connection. #4 after messinger sighned in les than 2 min from #2. #4 LW running good I think. #5 LW droped from 500KB/s to under 200KB/s. #6 connection lost

[Grandpa]

#3 was just after messinger started trying to sighn in but LW still showing connection.

[Grandpa]

#4 after messinger sighned in les than 2 min from #2. #4 LW running good I think.

[Grandpa]

#5 LW droped from 500KB/s to under 200KB/s.

[Grandpa]

#6 connection lost The entire sequince to less than 10 min.

[Grandpa]

There appears to be a direct correlation between # of simultaneous DL and disconnect problem. I can run 3 simultaneous DL varying between 350KB/s and 450KB/s for hours with no problem. But when I run 4 even if the KB/s # is lower which it is it appears that when #4 starts the KB/s starts drooping on the others they can be running steady at 100 to 150 per prior to starting #4 but drop to 60 to 110 after #4 starts.

Shortly after #4 starts within 5 min. I will totally loose connection at this point there does not appear to be any problem with the volume of KB/s thus far it appears to be # of DL. I am currently checking out limiting KB/s transfer rate will post results after I complete test.

[Grandpa]

What I found is that if I limit to 250KB/s I can run 4 simultaneous DL but if I raise the limit to 300KB/s I loose connection. I can run unlimited with 3 connections seeing DL at 500+KB/s. Let me know if you need stack traces running in different scenarios.
My current set up is.

Asus A8V Delux

AMD 64 X2 3800+ Over clocked to 2.55GHz Benchmarked and stress tested stable. MB temp 28C CPU temp 32C with LW running DL at 400KB/s avg. CPU usage between 0% & 3%

2 GB corsair ram PF usage 352 MB LW Debug 86,000K

eVga nVidia 6200 256 MB

2 – Fujitsu U320 74 GB SCSI hard drive

1 – WD 120 GB hard drive

Comcast Cable 750KB/s Down 45KB/s Up
Marvel Yukon 88E8001/8003/8010 PCI Gigabite Ethernet Controller,
Driver Marvel 9/19/05, 8.41.1.3
Digita Sig. Microsoft

Service: cable
Speed (advertised)5900 kbit/s:
Operating System: Windows XP
Connection: Normal

This test was run with LW off


1. Your Tweakable Settings:
Receive Window (RWIN): 148920
Window Scaling: 2
Path MTU Discovery: ON
RFC1323 Window Scaling: ON
RFC1323 Time Stamping: OFF
Selective Acks: ON
MSS requested: 1460
TTL:
(less any hops behind firewall) 130
TTL remaining: 114

2. Test 381601 byte download

Actual data bytes sent: 383061
Actual data packets: 264
Max packet sent (MTU): 1500
Max packet recd (MTU): 1500
Retransmitted data packets: 1
sacks you sent: 0
pushed data pkts: 61
data transmit time: 4.903 secs
our max idletime: 1761.6 ms
transfer rate: 71051 bytes/sec
transfer rate: 568 kbits/sec
This is not a speed test!
transfer efficiency: 99%

3. ICMP (ping) check

Minimum ping: 73.46 ms
Maximum ping: 76.51 ms
Ping stability:
73.63 75.16 73.53 76.51 73.46 74.00 76.29 74.50 75.36 73.91



Notes and recommendations:
RWIN is in range
Looking good

Notes and recommendations:
Good data stream (no/few rexmits)
1 second+ stall detected (FAQ #1606)

Notes and recommendations:
Looking good


Service: Cable
Speed (advertised)5900 kbit/s:
Operating System: Windows XP
Connection: Normal

This test was run with LW running 250 KB/s, DL 2 files, 27 host


1. Your Tweakable Settings:
Receive Window (RWIN): 148920
Window Scaling: 2
Path MTU Discovery: ON
RFC1323 Window Scaling: ON
RFC1323 Time Stamping: OFF
Selective Acks: ON
MSS requested: 1460
TTL:
(less any hops behind firewall) 130
TTL remaining: 114

2. Test 1024001 byte download

Actual data bytes sent: 1038601
Actual data packets: 713
Max packet sent (MTU): 1500
Max packet recd (MTU): 1500
Retransmitted data packets: 10
sacks you sent: 7
pushed data pkts: 130
data transmit time: 8.608 secs
our max idletime: 575.3 ms
transfer rate: 110005 bytes/sec
transfer rate: 880 kbits/sec
This is not a speed test!
transfer efficiency: 98%

3. ICMP (ping) check

Minimum ping: 77.81 ms
Maximum ping: 375.65 ms
Ping stability:
78.95 90.68 77.81 375.65 78.19 89.28 78.76 77.88 353.19 82.12



Notes and recommendations:
RWIN is in range
Looking good

Notes and recommendations:
Good data stream (no/few rexmits)
Notes and recommendations:
Looking good


I do not know that all of this is needed but what the hell is a test without a few stats

[zab]

Very good, detailed observations. The more like these we have, the sooner we'll be able to address this nasty problem.

[Grandpa]

Sorry zab I can't get any of the other P2P apps to go fast enough to rule out my computer. I can get enough files going but I cant get above 120KB/s with any of them.

[zab]

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

[Grandpa]

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.

[Grandpa]

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.

[Grandpa]

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.

[Grandpa]

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

[la croute]

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


la croute

[la croute]

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

[la croute]

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

[la croute]

this one is starting connection which never connected

la croute

[la croute]

here is the disconecting stack

la croute