Problem?

[runelord999]

I thought this was going to be an isolated incident, but I guess not.  This happened 3 times (and counting).

What happens is this: while using Shareaza, for some reason, after like 10 minutes, it hangs and freezes.  Cntrl + Alt + Del shows that the CPU usage is only at 5%  , yet the comp is basically frozen.  So I close Shareaza, and the strangest thing happens.  ashServ.exe (i think thats it  ) memory usuage swells like a balloon to 300 MB (yes, you read right...... ).  After reaching approximitly 300 MB, it promptly jumps back down to 16 MB  , but starts using 100% CPU usage :'(.  This requires a kill of the process and then its all good.

I don't know if this is Shareaza's fault, my fault , or Avast's fault, so I posted here.  

Using latest BETA (.536), WinXP Pro, Shareaza 2.1.  This happened before I installed the BETA too, soo.....  

[DavidR]

I don't know if this is Shareaza's fault, my fault , or Avast's fault, so I posted here.  

Using latest BETA (.536), WinXP Pro, Shareaza 2.1.  This happened before I installed the BETA too, soo.....  

5.36 is not beta, the latest version is 4.5.546, you will need to do a manual program update if you want it now.

This would tend to point to something else if has been happening previously. Do you have the latest version of shareaza?

[lukor]

Most probably it is Shareaza using some of the mail ports for something other than mails (eg. connecting to port 25,110,143 to fool firewalls).

You can enable logging in avMaiSv and see what is the name of the process which is causing the problem and then ingore this process from automatic mail scanning.

A) enable logging
  1) edit the Program Files\Alwil Software\Avast4\data\avast4.ini, find the section [MailScanner] and add the line Log=20
  2) restart the service "avast! Mail Scanner"

B) scrutinize the log file (Avast4\DATA\Log\avmaisv.log) or post it here

C) disable the offending process
  edit the avast4.ini, section [MailScanner], add the line IgnoreProcess=shareaza.exe -- replace with the name of the process, just the name, no path.

D) disable logging