Shareaza

At least I think it's caused by ed2k, since it never happened when I ran for ages with just G2 and G1 enabled.

After about 2 days of being continuously connected to one ed2k server (and a changing mix of G1 and G2 hubs) the UI was sluggish, no uploads or downloads were occurring, few downloads were queued, and the network tab was full of red lines, some saying "network core overloaded". This with the D #: U # numbers both below 1kb/s so there's no way anything should actually have been overloaded; it was using virtually no bandwidth. Timers on the network tab were not counting nor were the bandwidth numbers updating themselves, though the log area was generating new entries, mostly about dropped connections. Oh, and the thing was using 100% CPU.

I closed it, but there's still a Shareaza process using most of the CPU after half an hour.

What the f*@! happened?

Version is 2.5.2.0, which I'd thought was supposed to be stable.

I have\had a similar problem with 2.5.2.0 . Did you look into my topic 'Network Core Overloaded' ?
viewtopic.php?f=3&t=720
No solution was posted there, nor any usefull explanation of what 'Network Core Overloaded' actiually means .

I think it's version related, so I downgraded to 2.4.0.0 .
Shareaza is still hashing, on my 'slow' pc so connections are unstable so I can't tell but,
when it finishes hashing I expect everything to work fine again .

I will post my finding then .. which can take few dayz .

Got rid of the 'Network Core Overloaded' problem

Hope it helps; viewtopic.php?f=3&t=720&p=4951#p4951

If u find a different\better solution related to 'Network Core Overloaded' could u post it there then Thanxs .

Eeeuw. Sounds like a colossal pain when simply killing the process and manually restarting Shareaza suffices to make it work for another couple of days. I know people that reboot their whole operating system more often. (Mostly because they don't know how to get it to work semi-reliably.)

If you think ED2K is the culprit, have you tried running with ED2K disabled?

Oh, and what is happening is that some thread in Shareaza is using all the CPU and this makes everything else insanely slow, which makes network connections time-out and fail. You could try a clean re-install, since this might be caused by some file getting corrupted.

If it had been caused by a file being corrupted, simply restating Shareaza wouldn't have fixed it.

As for turning off ed2k, I actually don't usually have it on, but I'm hoping to find sources for a few rare files with it. It's worked so far -- two out of three particular rare files have completed and a third is close to finishing when all three had been languishing in Pendingville.

I did not mean the files in your library. Your Shareaza installation is composed of files such as "Shareaza.exe" and a bunch of DLL and DAT files. These are all removed and recreated from scratch when you do a clean reinstall.

It does not matter. If a disk file had gotten corrupted, quitting and restarting Shareaza wouldn't have fixed the problem; only some action that replaces the damaged file could have done so.

Since restarting Shareaza did fix the problem, I conclude that it wasn't caused by file corruption. Instead, a bug got triggered that put Shareaza into a state in which some of its internal functions had ceased to operate, which abnormal state restarting corrected.

Why don't u just do as I did ? Install a previous version you didn't had the problem with &Hope it gets fixed in a future release.

Updating doesn't necessarrily means better !

If it ain't broke, don't fix it ! Especially software !

&If u think that is a lot of work,... work on ur programming skills, it will save u time in the future !

2.4.0.0 had a raft of problems of its own that I don't want to put up with again.

Here's hoping 2.5.3.0 is better behaved than either.