My computer has been running rather slowly for the last several days so I ran a netstat command to see if I had an unusually large number of open ports. The netstat -b command shows NINE ports associated with ashWebsv.exe. Here is the relevant excerpt.
TCP asus-m3a:12080 localhost:1789 ESTABLISHED 2924
[ashWebSv.exe]
TCP asus-m3a:12080 localhost:1805 ESTABLISHED 2924
[ashWebSv.exe]
TCP asus-m3a:12080 localhost:1730 ESTABLISHED 2924
[ashWebSv.exe]
TCP asus-m3a:12080 localhost:1799 ESTABLISHED 2924
[ashWebSv.exe]
Also, Task Manager shows the ashWebSv.exe to have a Mem Usage of 80,808 K with a CPU usage of 0%.
I am running Windows XP SP2. I have 2 GB of memory on the computer. I can’t find a Help/About screen but the main control panel for Avast says the version is 4.8; the current version of the virus database is 100309-0.03-09.
Are these numbers (the number of ashWebSv processes shown by netstat and the CPU usage for that same process) reasonable? If not, what should I be doing to bring these numbers to a more reasonable value?
@ 0%, the CPU usage should be reasonable right? ;D as to the mem usage, you said you got 2GB RAM and avast using round 80 MB, that’s a bit high but it doesn’t matter. Main thing I wanted to say actually is that you should upgrade to Avast 5 www.avast.com/
The CPU usage of 0 is not a concern for me. I was mostly worried about the memory usage and the number of ports used by ashWebSv.exe. You say the memory usage of 80 KB is a bit high but not a problem. What about the 9 ports used by ashWebSv.exe: is THAT a problem??
By the way, I didn’t realize that Avast 5 was out. Shouldn’t the program have updated itself automatically to Avast 5? Or do the automatic updates only update the virus database for the version of Avast you are running?
OK be careful, don’t attempt to upgrade directly from Avast 4.8 to Avast 5. It’s possible but it’s also been a source of issues for many. So your best bet is to first uninstall avast 4.8 completely, reboot, and then install V5 from scratch.
Also, be aware that there are “sometimes” issues in XP, although officially V5 is 100% compatible, there is still a small amount of users reporting problems with V5 in Xp that Vista or Seven users never experienced.
Generally you may see a lot of tcp connections via localhost to avast and from avast to the internet to support whatever browsing you are doing. An http to a website actually generates a bunch of tcp connections to the individual addressable areas of your web page, which are then assembled into your web page by your browser. Pictures, ads, news articles for example tend to produce a very large number of tcps because they are often at different addresses on different servers. Ashwebsv just reflects this, as does netstat. You can often take a look at the source code (html) for your page with your browser and see a lot of what is happening for simple web pages with http’s embedded.
