that would be a good guess… if I ran a P2P program on my systems. I run
- secure shell
- firefox 3.0
- thunderbird
- FTP.
Heck I don’t even run yahoo or aim much less a p2p.
Hello again. This is how ashwebsv looks by me. Also, I’ve upload my firewall log, that you can see what ashwebsv trying to do.
I experienced this problem against last night at home, but I had decided not to post about it.
However, today I have experienced this problem at work. Also Windows XP but SP2 and very different hardware and software installed. The avast! On-Access Scanner reported that it had last scanned www.veoh.com/dwr/exec (it may have been longer but this is all I could see).
The same entires are appearing in the AshWebSv.ws log and TCPView shows the same odd number of listening entires all on the same IP/port.
I have been facing this problem for some days now and thought i could live with it until it got fixed or something but now it starts getting really irritating. It happens every day now and the only solution is to restart my computer. It always happens when i have firefox 3 (almost all the time) open and as other people said i have lots of connections in netstat when this occurs. It seems that this number keeps increasing (because i have connections like this even before ashwebsv starts hitting 50% cpu usage) and at some point when this becomes really big the problem occurs.
TCP 127.0.0.1:12080 127.0.0.1:42233 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42234 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42235 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42236 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42237 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42238 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42239 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42245 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42250 CLOSE_WAIT TCP 127.0.0.1:12080 127.0.0.1:42256 CLOSE_WAITand so on. I currently disabled avast (not uninstalled) hoping that you are looking into the problem. Can you please confirm you are looking into the problem and if you think it can/will be solved some time soon? Thanks.
Firefox will keep the connections open to increase speed.
High memory and CPU consumption is one of the reasons I do not use Firefox.
IE7 with IE7Pro works just as good without the Firefox problems.
By the way, TCPView will show you more information:
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
So, let me see if I understand this.
It’s not a problem with avast webshield. Even though it didn’t happen in a priopr version and does in the latest version.
It is a problem with Firefox even though the problem didn’t exist in the old version with Firefox, but does in the new version.
Wow! Thanks for clearing that up.
Firefox doesn’t change, webshield does, and the problem is Firefox’s fault.
As a former CTO, you don’t mind if I say that is the weakest excuse I have ever heard and I feel that it is a totally bogus response.
Couldn’t Lukas drop some light here?
I want to report, that i have same problem, but taskmanager gives me 80-90% of CPU usage and proccess ashWebSV.exe takes all resources.
only reboot solves problem for a while.
Could somebody give us a recommendation for solving this problem
i’m using Dell inspiron 6400, T2300, 2GB RAM , progs: firefox 3.01. chrome, IE7. emule.
Can somebody to answer to this problem? avast tech. stuff are u here???
It’s beyond my knowledge. I need Lukas here…
on September 20, 2008 I uploaded the dump file to the FTP site. Did anyone even try to see what it showed?
If this is a FF issue with the latest version of avast, the answer seems to be “stop using webshield”, but that’s just a kluge. The real answer may be hidden in the dump I sent, but since no one ever said if they grabbed it or looked at it, it seems we will never know.
That’s too bad. :-[
Hello Met,
sorry, we have indeed looked at the dump. WebShield cycles in the listen / accept code, with errors returned by WinSock. The reason why WinSock (or some other component) refuses to provide sockets for WebShield is beyond the dump. 
Lukas
Thank you for letting me know that it was not a dump in vain.
right now, avast’s ashwebsv.exe takes 62,590K and CPU 39-78
i stopped all proccesses and switched them again. but pc slows down , sites are didn’t opened right away. only reboot will solve the problem.
It is only using 12,140K currently with a Peak Mem Usage of 35,264K for me but then I do not use Firefox.
I’m having much the same problem with Avast! eating up tonnes of CPU time and making browsing in Firefox less than ideal. So far the only solution is a reboot. Not all that cool when I’m having to do this multiple times a week.
I demoed this product for a couple weeks and didn’t see any real issue with this and thus purchased a bunch of licenses for the machines here at work.
All machines running XP current, of varying hardware specs. All running Firefox 3.0.x, and Internet Explorer has been banned from use as per corporate policy (my policy).
I need a resolution sharpish.
For what it’s worth, I’ve reinstalled the software about 3 billion times (it feels) and the problem seems to be getting worse. This seems to be affecting FF a whole lot more than IE (I can’t say I’ve heard complaints about it affecting IE, but the users know that they aren’t to use IE for anything other than one specific task). Disabling the webshield wouldn’t be an optimal solution as that was one of the reasons I went with Avast.
I will perform a dump of the process the next time it inevitably happens.
At this point, we have shown a number of users are having the problem. We have shown the it is happening on XP platforms using FF We have shown that it is NOT intermittent
And now we know that it is not just us freebe’s, but the same problem is showing up in the purchased product.
Now, I don’t work at Avast, but I am a former CTO. If I was the Avast CTO I would get a few computers with configurations that matched those that have reported the problem and set them up to duplicate it. Then I would take a few of my top engineers and look at the changes that were made in the CVS to see what portions of the code that were changed could be generating the defect. This is what you do when you have a baseline that works, and then a release that doesn’t. It’s not rocket science, it’s computer science and it’s why we have change control systems. They allow us to see just what was changed to take a working system and make it a broken one.
What is not going to work, for our friend in Canada or for many others, is taking a head in the sand attitude that somehow the changes made to the code are the users fault, and that the failure is on our part.
No anger here, just a deep sense of frustration that it has been over two months and it appears that Avast is saying to us “Too bad, learn to live with it.” :-X
Does the latest beta (http://forum.avast.com/index.php?topic=39392.0) behave better?
Can’t say I’ve tried. I don’t like running beta on production machines, especially ones that do real work.
Which avast version are you using?