cmdagent.exe uses alot of ram!!!

is this normal??

i installed the full CiS4 suite,

seems using alot of ram dont you think?

can be the AV part of it?

shall i set the AV to STATEFUL or ON ACCESS???

thanks guys :smiley:

That can be normal when the AV is updating, but you definitely shouldn’t be seeing that much memory usage under normal operation.

In stateful mode, you may get a marginal performance improvement. In this mode, the AV will not scan a file again unless it has changed or the virus database has been updated. I say you may see a marginal performance improvement because the AV database can be updated every 30 minutes. So unless the file is an often accessed OS file, you aren’t likely to see much improvement if the flag is reset every 30 minutes.

ok so anyhow, user should set it to StateFul then?

and what about the Heuristics?

i should set to HiGH?

and also, 2 hours have past, and cmdagent.exe is still running at 110MB+

any idea how to make it calme down?

**note that i have Shadow Defender installed too…



It’s all down to user preference whether you want to run stateful or on-access.

I would leave heuristics on low. You’re going to see a lot of false positives if you set it higher.

Is Shadow Defender an AV? It’s not a good idea to run more than one active AV on a system.


Shadow Defender SandBoxes your entire OS,

Do you have the sandbox enabled?

Nope… Any other idea?

This might be a bump but I kind of need help. Everytime on start up cmdagent.exe is hogging about 500MB RAM and keeps going up and up until XP fails and resets the amount you can see back to 5 MB. But then it just keeps on going. Right now it’s supposedly back to 2.544 kB but looking at my used RAM, I’d say it’s still using about 500…

XP has multiple issues with showing RAM usages correctly. XP also does this to steam and firefox.

I only use the Firewall and defense+. Safe mode and Clean PC. Any ideas?

What do you mean with “XP has multiple issues with showing RAM usages correctly. XP also does this to steam and firefox.”?

Can you be more specific? Does the same thing happen with FF and Steam; as in use all available RAM and that brings Windows to its knees? What do you mean with issues showing RAM correctly?

Is your Windows up to date? Are drivers up to date? Is your pagefile enabled?

I have pagefile enabled, my windows is up to date. And what I mean by that is that at some point when a program is using a lot of RAM, XP can fail to correctly show the amount. This happens with Firefox, Steam and comodo. Also games. Basically what happens is that XP first shows it correctly. The RAM keeps going up and up until it’s at it’s peak. About 500 or whatever the amount it is that the program uses. (Has to be over 150 MB RAM.) Then XP shows behind the programs name that it uses 5 MB or at least any low number. BUT, on the bottom of the task manager you can clearly see that the amount of total ram used hasn’t gone down. That is what I mean with “XP has multiple issues with showing RAM usages correctly. XP also does this to steam and firefox.”

But this doesn’t really answer my question because the point is that Comodo 3 AND 4 are using way too much RAM.

I see what you mean now.I have never seen that before and my first idea would be that it may be Windows things since it effects there different applications.

Do you see the same thing happening when you use Process Explorer for example?

How much do cmdagent, FF and Steam use when their memory usage peaks. Can you post screenshots of Task Manager in various situation?

How much RAM does your system have?

Cool. Process explorer actually confirms what I said. XP thinks or allocates the programs to the amount of RAM you see behind the process itself. But they use more. Which you can see with Process explorer as “private bytes”. Perfect. I’m in the cool because I’m backed up now. The help screen even says that when the private bytes exceed the working set. Then you have a program with a memory leak. As of the making of the screenshot firefox is doing fine. Steam.exe, cfp.exe, cmdagent.exe and ashServ.exe are in fact not. (ashServ.exe is part of Avast.) The private bytes are kind of alright now but at start up they are INSANE for cfp.exe and cmdagent.exe.
So… Fix nao plox?

P.S.: I have 1024 MB RAM. DDR2 5xx MHz.
Screenshot for great justice proof!

With Task Manager you can show much more than it shows by default. Just look under View → Select columns.

Is cmdagent still using 500MB during each boot? Are you willing to try a clean install to see if that helps or not. Before doing the clean install you can export your current configuration and import it after installation.

What you are seeing on the screenshot already IS a clean install. And I really think that the point here is that Comodo has a memory leak issue.

Same here. Windows 7 x86 starter on Asus Eee, 100+ MB memory utilization, degraded performance.

cmdagent.exe uses 130mb of ram constantly on W7 32bit.

Plus after I installed the full CIS suite my pc got very slow. It wasn’t like that when I had only firewall installed.

Usually CIS runs very light. I checked my stats of cmdagent and find comparable figures but my system runs snappy and responsive. See attached image.

That means there is a problem but we are not looking in the right place.

Best thing to do to make sure that there are no left overs of previously uninstalled security programs around. Not all uninstallers do a proper job. And left over applications, drivers or services can cause all sort of “interesting effects”.

Following one of two of my tutorials to make sure there are no more left overs.

Use existing removal tools

Try using removal tools for those programs. Here is a list of removal tools for common av programs: .

Otherwise do a Google search with terms “removal tool” and * name of product or vendor*.

[attachment deleted by admin]