Shareaza

Considering that I haven't installed anything newer over my months-old copy of Shareaza 2.7.8.0, I find it strange that it keeps sprouting new bugs. The latest began to exist 2-3 days ago, and affects G1 discovery services.

Specifically, it keeps forgetting them. If I leave it running a few hours to overnight I'm liable to come back to it to find it not connected to G1, not trying to connect to G1, with the G1 hostcache empty, and no G1 discovery services listed. If I add the ten or so working G1 discovery services listed at http://gwebcaches.pongwar.com/gnutella.html there will typically soon be G1 hosts in the host cache again and Shareaza will connect to G1 again soon. But a day or so later it's back in the same broken state with no G1 discovery services listed and an empty G1 cache.

What is going on? And is there any way to "nail" a discovery service entry in place so I don't have to keep manually adding it back on every day or two? I tried right clicking one after adding it but there's no "pin item to list" type option that I could see to make an entry immune from expiring, or whatever it does.

I can only presume that G1 discovery service entries can expire over time, and normally get auto-refreshed by being freshly discovered via peer discovery, but that that's stopped happening or something similar has gone wrong. Maybe the problems with poor G1 connection handshaking success rate have crossed some threshold that causes it to lose G1 peers and discovery services faster than it gains them via peer discovery, so the G1 hostcache and discovery services wither away over time now instead of remaining robust.

Regardless, version 2.7.8.0 has serious problems with G1 that did not occur in earlier versions, a regression that begs to be addressed.

It just happened again. That makes three times in as many days. For weeks before this Tuesday not a single similar incident occurred.

Something has changed, as of three days ago. Somebody changed something. I didn't change anything; therefore someone else did.

Change it back.

I want to know what is being done about this issue. So far as I can tell, reporting problems with Shareaza here is like throwing stones into a black hole. Prove to me I'm wrong. Fix this.

Help us to help you.

Sorry but Shareaza cannot fix your connection problems.

That's it, no changes was made in Shareaza G1 code from previous version (i.e. since Dec 2014).

BTW How often you had reboots computer (sleep and hibernate are not counts as reboot)?

Why you reinstalled the OS?