Shareaza seems to have problems with putting PC in standby and waking up the day after.
Because these problem[s], i developed the practice to restart Shareaza when i wakeup the PC from standby.
I only will put down the 'difference-behavior' comparing 'clean start Shareaza' or 'standby-wakeup':
Behavior problem with shareaza 2.5.2.0 (stable release) (i observed this multiple times):
In standby-wakeup, shareaza generates alot of upload traffic bandwidth and packets per second.
This traffic does not directly come from current uploads. I took this values: upload bandwidth from the resident status bar at the bottom (that is meant to represent the combined upload) compared to upload bandwith from upload window (which is meant to be only the file upload bandwidth).
I see status-bar upload is much higher, almost not in a correlation to file-upload bandwidth. Combined upload goes to the limits (40KB), while file upload may be close to zero. Also the amount of packets generated is high, like 200 packets per second (measured by some other network monitoring tool).
This is an explanation which i think might be reasonable:
Shareaza doesnt recognize the standby-wakeup, but it thinks it has an uptime like 2 days, so it may think: hey i am long--time-online, so lets switch in master hub mode.
When i restart shareaza, i see statements in the network log panel like '...blablabla... shareaza is in shielded leaf mode, rejecting request'. This may be from other clients which think this node is still in master hub mode, which is then rejected by my restarted Shareaza.
Behavior problem with shareaza 2.5.2.2_Win32_Debug_r8581_2010-04-21 (i observed this only one time today):
Shareaza crashes. sorry, i clicked error window away
Laters
Al