.7x stops sending packets, buffers fill
 

Here's something that started with .70 and has carried on to .73. After gnotella's been running awhile, it quits sending packets to the active connections. The packets all go into the buffer instead of actually being sent out, and eventually the connections get dropped.

When new hosts are added from the host catcher, the connection is opened, but Sent/Rcv/Drop all remain at 0, and the packets start to pile up in the buffer. One by one, all the hosts in the host catcher are dropped, and eventually the client's left sitting there idle.

Quitting and restarting the client gives a "port already in use" error, so I end up having to quit/restart/change port fairly often.

Shaun

My mistake, it's incoming packets which are piling in the buffer, not outgoing. A screen shot showing 2 hosts with this problem is below. If I leave it going for awhile, the other two hosts will exhibit the same problem, then on to the host catcher hosts, etc.

http://gnucache.eyep.net/buffer.gif

Shaun,

What sort of machine are you running? I noticed this problem often on my 166, but on my spiffy new PIII 750 laptop w/256 megs of ram (nice company, good company!), I never see it anymore. Never. I've noticed other tidbits that go awry on the 166 (scrollbars do some *weird* stuff), but all is well on the laptop.

PIII 600, 192MB RAM. It doesn't seem to be a resource issue, at least not a global resource issue; the same thing happens even if I run Gnotella on a fresh reboot. It's an oddity I haven't seen with any of the other clones, either.

Does your company wanna buy me a new laptop too? http://forums.gnutellanews.com/wink.gif I could do some more testing.

Shaun

I have the same issue. I'm running a AMD K6 running at 367mhz and 160 Meg of RAM. It's a Toshoba portable model 2060CDS. It's connected to the Internet via DSL 70k up 512k down.

Forgot all the info....
Windows 98
V .73

Still happens on a win2k 500mhz dual xeon.

it may be a win2k issue, or the fact vb is SLOW compared to c++ with mfc

I forgot to mention that I'm running Win98, so it's not a W2K-specific problem.

Shaun