Author Topic: ashWebSv.exe locks CPU at 100%  (Read 3516 times)

0 Members and 1 Guest are viewing this topic.

saph03

  • Guest
ashWebSv.exe locks CPU at 100%
« on: April 08, 2007, 08:41:30 AM »
ashWebSv.exe has been running at 100% CPU (50% of a dual CPU machine) for a long time (hours?).

Attached is a screen shot of Task Manager.  I'm not sure what other information to provide to help analyze the issue.  I'm running Win XP Pro x64.

I did "Stop on access protection", but the process remained running.

I killed the ashWebSv.exe from task manager, and restarted on access protection and the CPU returned to normal.

I had noticed strange hitches in my mouse motion, and the restart seems to have resolved these.




Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88854
  • No support PMs thanks
Re: ashWebSv.exe locks CPU at 100%
« Reply #1 on: April 08, 2007, 02:27:53 PM »
I have only experienced this once and that was only a couple of days ago, I am however using the latest avast beta, 4.7.971 and on XP Pro 32 bit.

Something and I know not what that was cause web shield to effectively hang, terminating the provider didn't achieve, the service was still running in Task Manager. Unlike you I went to the Administrator Tools, Services and stopped it there and then restarted it at the same place. I had to restart the Web Shield provider also and everything back to normal and no recurrence since then.

What version of avast are you using ?
Does this happen on a regular basis ?

Even at present in you image the CPU of 53% seems high, what were you doing at the time ?
Mine CPU drops to 00 when not actively browsing like it is whilst compiling this reply, see image.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.2.6105 (build 24.2.8918.824) UI 1.0.799/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re: ashWebSv.exe locks CPU at 100%
« Reply #2 on: April 08, 2007, 03:11:23 PM »
Please, activate logging in WebShield:
1. Edit <avast>\data\avast4.ini file
2. Find the section [WebScanner]
3. Add the line:
    EnableLogging=1
4. Restart Web Shield in XP (terminate and start again) or whole PC in case of Win98
5. Browse (trying to access some webpages)

The log file are <avast>\data\log\ashwebsv.log and ashwebsv.ws.
They would be accessible when WebShield is terminated again.
Post them here or send by mail to rypacek (at) asw.cz
After that, disable the logging to avoid a big log file.
The best things in life are free.

saph03

  • Guest
Re: ashWebSv.exe locks CPU at 100%
« Reply #3 on: April 24, 2007, 08:45:06 AM »
I'm using Avast 4.7.986 on Win Xp 64bit
The CPU bound lockup has not recurred.
I've enabled logging.

Offline alanrf

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3870
  • Just an avast user
Re: ashWebSv.exe locks CPU at 100%
« Reply #4 on: April 24, 2007, 09:14:43 AM »
The window you posted did not show all the processes on your system.  Are you using any form of P2P software on your system or perhaps some type of streaming content connection?
« Last Edit: April 24, 2007, 09:18:48 AM by alanrf »

saph03

  • Guest
Re: ashWebSv.exe locks CPU at 100%
« Reply #5 on: April 26, 2007, 05:53:13 AM »
Its a fairly clean XP 64 bit install.  No browser add-ins, not even Google Toolbar.

Installed software of possible note:

Skype
Citrix GoToMeeting
Visual Studio 2005 (for developing C# .Net web apps)
SourceGear Vault client (source control with Internet connection to repository)
Outlook 2007

I'm sure that Skype and GoToMeeting were not active when the CPU was locked.  However, it is possible either a Skype phone call or a GoToMeeting had been done earlier before the 100% CPU was noticed.

Offline alanrf

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3870
  • Just an avast user
Re: ashWebSv.exe locks CPU at 100%
« Reply #6 on: April 26, 2007, 06:34:02 AM »
I'm not an X64 user but I do use Skype to talk to my son in the UK and that never causes a blip on avast and avast is not scanning the ports used by Skype.

I guess we will have to await another incident and what is shown by the log