I knew it! I just knew it!
What a waste of time.
cmdagent still eating cpu.
GUYS! Please!
If something is not in changelog and if something is a problem for MANY YEARS that means - IS NOT FIXED!
Isn’t it obvious?
The same problem, no matter how many times you recommend to install “updated version”, “beta version” or ANY OTHER version! This cmdagent will be stuck on high cpu no matter what! You know why?
BECAUSE is bad written! For years! Sure - if you test it by using your computer for browsing Facebook and sending small emails to your friends, it will probably work. But really - try some hardcore work including opening lot of programs that utilizes internet connection, then close them etc. After 10 hours of working (yes, I am work a lot, computer is not just my hobby, is also something I must using all the time in my work) it will begin behave like that.
So now, after I finally proove that I had right and problem exists not because I am not tried some beta/sheta/whatever magic version (magic, because according to Comodo stuff here, it MAY work just because version number increase), but because Comodo Firewall has a bug. Bug that nobody cares and probably not even single programmer tried to fix. For years.
I suggest two things:
- Stop giving advices like “update Comodo” if you’re not absolutely sure that it contains specific fix, otherwise you’re just wasting people time.
- Or just release another version with bigger number without any changes - who knows, maybe version number is very important and problem somehow disappears.
I am disappointed and a little angry, because I bet that meanwhile I was testing two or three versions (including beta), not even single programmer review single line of code to find this problem.
But seriously - just add option to restart cmdagent.exe - it will be at least working workaround. And I think not very difficult to write. For sure better than restarting computer.