I use cygwin quite a lot and when I start a shell (zsh), more often than not it takes a long time and the CPU spins at 100% with cmdagent.exe being the culprit. cygwin pulls in a few dll’s and starting a shell causes running a few of the cygwin executables. After the shell starts, starting it again is fast for a while but then it’s slow again. I suspect this is because of the stateful setting of the a/v. These cygwin files do not show up under ‘unrecognized files’. Any way to speed up this cmdagent real-time scanning or is this a bug in the A/V?
If that’s the case you can disable the automatic update of AV.
If you want to have more control over the updating of the AV then there is workaround. Make scheduled scans that scan a folder with only a small file in it and set the AV to update when doing the scheduled scan. That way you can control the AV updating.
Is there a way to tell what cmdagent is doing when it’s hogging the CPU? Is it doing an a/v scan? Is it trying to submit something to the cloud? D+? etc
This seems to have started with the upgrade to 5.3, I did not notice this problem before.
I emailed the crash dump and didn’t bounce so I assume it went through. I’ll file a bug too, though I can’t reproduce the crash, but I can always reproduce the slowness on multiple machines.