Some problems with Shareaza

[branko-r]

[raspopov]

Use bug ticket system please: https://sourceforge.net/apps/trac/shareaza/report/1

[gs75081]

Just curious whether there are any new revelations on the 2.6.0.0 x64 random freezing issues.

I've changed hardware, operating systems, cables, router and network adapter settings settings, tweaked, twiddled, everything I can possibly try. These observations are consistent across:

XPSP3, W7 Pro, Vista and WHS2011.

Linksys, D-Link and Netgear routers at both 100 Mb and 1Gb.

With or without traffic shaping or QOS enabled at either the NIC adapters or within the routers.

With or without the AIO-ASF.

At completely random times the GUI hangs in a 'soft lockup'.
About 50% of the time it will not auto-recover, and the duration of the softlock is anywhere from one minute to over 30 minutes.

It may happen by itself with no interaction, but happens more frequently when attempting to search, browse other users, open or close upload or download windows or the cache window, or even when simply auto-arranging the window views.

It happens when other users access the server Shareaza is running on, or with no users accessing it at all.

I keep one graph window open with a 10 second refresh, watching only upload-download speeds and oddly enough, 95% of the time the graph and message monitors continue to respond, though both graph lines are frozen.

It happens whether G2 is the only protocol engaged, and in each freeze it dumps all G2 connections, whether in leaf or hub mode.

More the 75% of the hang periods continue to try processing requests, but fails indicating "network core overloaded".

All other GUI windows become unresponsive, and to attempt any change to settings or pressing the disconnect button results in a hard application lockup.

At times I see up to four or five Shareaza icons stuck down by the clock, indications that the program has restarted, even though I have no automated restart provisions enabled in or out of Shareaza.

About 25% of the time I will see a bugtrap generated, but no data is collected so I do not know how to send its data.

No other network or Internet anomalies have been observed, and the server itself is 100% responsive to its other applications, services and operations - I only see the problem if I happen to be watching the console.

FWIW, 2.6.0.0 x64 has never exceeded 10% CPU usage in or out of the fault condition, it has only used one of the 4 available cores (on the WHS2011 machine) and has never exhibited any abberant HDD abuse (as others have reported).

All platforms were absolutely 'dry', meaning no other applications or unneccesary services were engaged.

All operating systems report the same two logged errors, and here's the WHS2011 dumps:
---
ERROR 1000:
Faulting application name: Shareaza.exe, version: 2.6.0.0, time stamp: 0x4fcccd97
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x2444
Faulting application start time: 0x01cdc8cac8411331
Faulting application path: C:\Program Files\Shareaza\Shareaza.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
For a total of 69 errors in 70 days.
---
ERROR 1002:
Log Name: Application
Source: Application Hang
Date: 11/22/2012 5:12:10 PM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: WHS
Description:
The program Shareaza.exe version 2.6.0.0 stopped interacting with Windows and was closed. To see if more

information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 3598
Start Time: 01cdc8fb97222171
Termination Time: 0
Application Path: C:\Program Files\Shareaza\Shareaza.exe
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-11-22T23:12:10.000000000Z" />
<EventRecordID>69582</EventRecordID>
<Channel>Application</Channel>
<Computer>WHS</Computer>
<Security />
</System>
<EventData>
<Data>Shareaza.exe</Data>
<Data>2.6.0.0</Data>
<Data>3598</Data>
<Data>01cdc8fb97222171</Data>
<Data>0</Data>
<Data>C:\Program Files\Shareaza\Shareaza.exe</Data>
<Data>ff6d1eea-34f9-11e2-aaa3-001517226eb0</Data>


<Binary>430072006F00730073002D00740068007200650061006400000044006500610064006C006F0063006B0000000000</Binary>
</EventData>
</Event>
For a total of 43 events in 70 days.
And in 'Friendly View, the word bytes report it as a 'C.R.O.S.S.-.T.H.R.E.A.D..D.E.A.D.L.O.C.K.....'.
---

I've never approached the bug tracker system, since with all these observations I'd have no idea how to classify it (them?).

All I'm hoping is that I've provided enough info to help track down the issues. I believe in the future of Shareaza to continue being the best in P2P software. The fact that it has survived to this point is proof that the coders still believe in it too.

And, a happy Thanksgiving! Okay, I'm done. Nothing follows. Peace, out.

[gs75081]

Sorry, double-submitted post. Disregard this entry.