Author Topic: ashServ.exe memory usage  (Read 86692 times)

0 Members and 1 Guest are viewing this topic.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86949
  • No support PMs thanks
Re: ashServ.exe memory usage
« Reply #15 on: August 27, 2009, 01:47:22 AM »
Try compressing (zip) the dump file as I believe it should compress reasonably well.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.9.6034 (build 22.9.7554.734) UI 1.0.728/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Joost

  • Guest
Re: ashServ.exe memory usage
« Reply #16 on: August 27, 2009, 02:23:04 AM »
I did something wrong. :(

I thought maybe I can restart and make a new smaller one. But the old one is overwritten and I don't have it anymore (and I can't make it again of course).

But can't it just be the newer browser Google Chrome?
« Last Edit: August 27, 2009, 02:34:35 AM by Joost »

popish

  • Guest
Re: ashServ.exe memory usage
« Reply #17 on: August 27, 2009, 11:21:48 AM »
It is not the browser, I tried with both IE and FireFox.
Every action of the either browser causes the "private bytes" to go up. Even a refresh. And it is never released.

Had to boot, now watching the numbers go up again.
I terminated the "web shield" and it stopped going up, but the space was not released.
Why is the web shield affecting ashServ.exe and not ashWebSv.exe ?

Joost

  • Guest
Re: ashServ.exe memory usage
« Reply #18 on: August 27, 2009, 12:36:06 PM »
Ok, I restarted, did a few refreshes in a browser, made a dump, and uploaded it. It isn't that big but maybe you can find already the problem. It's named ashServ_Joost.zip
« Last Edit: August 27, 2009, 01:11:00 PM by Joost »

popish

  • Guest
Re: ashServ.exe memory usage
« Reply #19 on: August 27, 2009, 01:52:39 PM »
Me too  ;D

Dump of ashServ process created with userdump.exe because hangrep.exe failed.
Uploaded to your ftp server - ashServ_mem_2post47965.zip
(note - the first attempt failed so you may find half a file with a similar name).

Thanks

maxxx126

  • Guest
Re: ashServ.exe memory usage
« Reply #20 on: August 27, 2009, 07:16:36 PM »

Not much will to fix this problem it seems....

I uninstalled Avast from the control panel and ran the avast! Uninstall Utility mentioned in #3 and then reinstalled it. It improved things quite a bit, now Avast is using "only" 276 MB of virtual memory compared to about 1GB before but it is still quite a lot.
Had to reboot 3 times in order to do it.

Maybe I'll try the beta 5.0 when I have some time...

R2-D2

  • Guest
Re: ashServ.exe memory usage
« Reply #21 on: August 28, 2009, 04:00:38 AM »
Same here... 400 MB of virtual memory, and 200 MB of 'real' ram. Way too much for me.
I'v sent the dump file to ftp, hope it helps.

Here is a screenshot:



Another thing i notice, on my last complete scan, avast was saying 99% for hours... and process shown as using 1GB of ram!
After quit scan, of course the process was gone, but some time later (few hours) i notice this ashServ eating my precious ram.
« Last Edit: August 28, 2009, 04:04:01 AM by R2-D2 »

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86949
  • No support PMs thanks
Re: ashServ.exe memory usage
« Reply #22 on: August 28, 2009, 02:49:23 PM »
Your image shows a utorrent running and that will have a hit on ashServ.exe

- the uTorrent option in the P2P shield is unchecked by design because of the way utorrent works.
Quote from: Vlk
This is by design. Basically, µTorrent scanning in avast is suboptimal and we decided to turn it off by default (this applies to both Normal and High sensitivity levels). To be more specific, if µTorrent scanning is on, and you're using uTorrent to download large files, ashServ.exe will hog your CPU. This is because uTorrent closes/reopens the target file after transmitting every chunk, forcing avast to keep rescanning it periodically.

So if you have enabled utorrent in the P2P Shield you will see this increase in the ashServ.exe, the main scanning engine of avast. If you have, then it would probably be better to uncheck the option in the P2P Shield and have utorrent have avast (ashQuick.exe) scan the completed download.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.9.6034 (build 22.9.7554.734) UI 1.0.728/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Joost

  • Guest
Re: ashServ.exe memory usage
« Reply #23 on: August 28, 2009, 04:10:10 PM »
Any progress in fixing the problem?

I don't have µTorrent and the problem is NOT about CPU.

R2-D2

  • Guest
Re: ashServ.exe memory usage
« Reply #24 on: August 28, 2009, 04:22:30 PM »
Thanks for the explanation DavidR, had utorrent checked, now i'v unchecked.
However the ashServ.exe still using same amount of ram. :(

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86949
  • No support PMs thanks
Re: ashServ.exe memory usage
« Reply #25 on: August 28, 2009, 05:13:23 PM »
Any progress in fixing the problem?

I don't have µTorrent and the problem is NOT about CPU.

Sorry other than what has been suggested no.

My answer as directly to R2-D2's post and his was both memory and cpu.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.9.6034 (build 22.9.7554.734) UI 1.0.728/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86949
  • No support PMs thanks
Re: ashServ.exe memory usage
« Reply #26 on: August 28, 2009, 05:15:50 PM »
Thanks for the explanation DavidR, had utorrent checked, now i'v unchecked.
However the ashServ.exe still using same amount of ram. :(

Have you rebooted after that, though I don't think it necessary, but the P2P application still being loaded may continue with the previous settings. You could also Stop the P2P Shield and then Start it again to reload it with the new settings.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.9.6034 (build 22.9.7554.734) UI 1.0.728/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

R2-D2

  • Guest
Re: ashServ.exe memory usage
« Reply #27 on: August 28, 2009, 10:00:24 PM »
Rebooting decreased significantly the used ram!  :D thanks.
I'v disabled the p2p shield. however ashServ is still using using 72 MB ram and 190 MB of virtual memory.
« Last Edit: August 28, 2009, 10:02:34 PM by R2-D2 »

popish

  • Guest
Re: ashServ.exe memory usage
« Reply #28 on: August 28, 2009, 10:19:17 PM »
It is the web shield - disable option "enable web scanning" and it stops eating the memory.

I would appreciate it if someone can tell me -
1. What does "web scanning" do and what can happen now that I disabled it ?
2. Why is that affecting ashServ.exe and not ashWebsv.exe ?
3. Is someone working on the dumps we supplied ?

I really cannot continue with this - having to boot twice a day.
Is anybody doing anything ???????????????

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re: ashServ.exe memory usage
« Reply #29 on: August 28, 2009, 10:23:00 PM »
It is the web shield - disable option "enable web scanning" and it stops eating the memory.
Of course... you're just disabling the scanning, without scanning, no resources are taken, but no protection is given.

Why is that affecting ashServ.exe and not ashWebsv.exe ?
The core engine is affected as the scanning is performed by ashServ.exe.
The best things in life are free.