avagent cpu bound

[igor]

Could you identify the problematic archive, which should be close to (or rather shortly after, as Vlk explained) the end of the report file when full logging (i.e. including the "OK files") is specified?

[gprzybyl]

How would I determine what file avast is currently scanning?  Does it scan in alphabetical order or some other order?  My understanding is that files that are logged are the ones avast is finished with.  So I could look at the next file after the one that is scanned?  Would turning details on in standard shield do it?

[Vlk]

Do you think you could isolate the file that's causing the problems?
It should be pretty easy with a local aswCmd.exe scan (the name of the problematic file should be displayed on the screen at the moment of the hang).

BTW it might be the CHM unpacker. I've heard that it may contain some problems (at least in the version you're using).

BTW2 I know updating from RC2 to RC2a does not work for the AMS/console. But what about the clients? If it doesn't work, can you post the corresponding setup.log file?


Thanks
Vlk

[igor]

Well, I think avast! doesn't do any sorting of the files to be scanned - but as far as I know, the API functions enumerating the files return them in alphabetical order on NT-platform. So, I think you can expect them to be in alphabetical order (at least you can check by the previous ones).
You are right that if avast! freezes on a file, it wouldn't get logged; however, you can judge by the previous one (if the problem occurs after the first file of the archive, even the previous archive files should be there).

The easiest way to find out is to turn on the creation of the report files for the particular task (and set the "OK files" to be included there as well). Or, try to use aswCmd with the corresponding command-line.

OK, Vlk was faster ... and checking the aswCmd window would probably be the easiest.

[gprzybyl]

I tried one client update it worked fine.  

I'll rerun the command line scan.  I don't remember the name of the file but it was a .dll .  I'll see what it comes up with this time.

[igor]

Any news on the problem?

[gprzybyl]

 I reran the command line scan after upgrading to RC2A.  aswcmd.exe once again maxed out the cpu.  This time on a file named Unnamedstream.exe in spysweeper.exe .  This is a different file than the one previous which was a .dll .  Hitting esc does get you out of it and it cleans itself up.