First post from a Comodo beginner ( but a 20-year IT industry veteran )
Apologies if this issue has been discussed previously, but so much of the cmdagent-related discussion on the forum seems to be surrounding a CPU hogging issue with Comodo A/V updates that I’ve not managed to find anything related to any other aspect of cmdagent.exe resource hogging. So:
Comodo Firewall - 3.12.111745.560 - No other Comodo products knowingly installed, especially A/V ;D
I ditched Zone Alarm a few months ago in favour of Comodo looking for something a little less temperamental. I still believe Comodo F/W fits the bill but for me it comes at a price.
Pre-Comodo, my PC would boot and load all selected apps in about 3-4 minutes. Slow for some maybe, but OK for me.
Now, with Comodo in the picture, power-on until the machine is settled and ready to use is always at least 21 minutes.
Monitoring startup using Task Manager I can see that cmdagent.exe is extremely memory-hungry.
Incidentally, in that 21 minutes, cmdagent.exe accumulates around 50 CPU seconds though is rarely above a few percentage points of CPU usage which for me doesn’t represent much of a problem.
However, memory use seems to be a big problem and moreover, the way it uses and then frees memory is truly odd.
Bearing in mind that I have 1GB RAM:
- cmdagent.exe starts and memory use slowly ramps up to around 400MB
- memory is then released and usage drops to about 20MB
- usage ramps up again to about 360MB
- memory is then released and usage drops to a few MB.
- usage then ramps up again to an eye-watering 480MB in just a few seconds
- finally, cmdagent.exe releases almost all memory and settles on about 2MB
hard disk activity more or less ceases at this point which I take to be the end of serious page file I/O.
My (fairly self-evident) questions are therefore:
- what does cmdagent.exe get up to at startup and why does it take such a long time to do it ?
- what’s that roller coaster memory usage all about ?
- can I do anything about either of them ?
By the way, I read somehere that disabling automatic update checking might reduce this problem, but it made no difference.
Many thanks for any enlightenment on offer.
With very best wishes,