Hello! One month later I’m literally dying of curiosity…
1 Like
Hi, I’m back to Comodo, and with latest 12.2.2.8012 the issue still persists.
My RAM drive is about 800MB and I’m not using ImDisk.
1 Like
Using 12.2.2.8012 Firewall only.
I’ve created a NTFS RAMDisk with ImDisk on Windows 7 Ultimate 64-bit and copied some random files back and forth. ImDisk NTFS RAMDIsk is working fine for me, no high CPU usage.
It is randomly happening and in some cases it took a few days of running to see this issue for me, so it might be why you can’t see it.
RAMDrive is heavily used for storing temporal files.
As Digitama ans FN2PGF reported similar issue, it is clear the issue does exist at least in some conditions. I also see similar reports in Japanese BBS too.
I sent requested log about a year ago. It’s a quite disappoint to see nothing had changed since (including forum reactions :()
1 Like
Maybe you are right, as I just did a quick file copy test the issue did not occur on my end but it might if I would run it longer and if used to store temporal files.
Have you ever seen it happen right after system boot or only after some days of running?
Do you know ways to trigger the issue to happen immediately?
In general, issues are difficult to fix when they only occur at random intervals and in random conditions maybe that’s one of the reasons why Comodo needs more time to find the cause and to fix it.
Unfortunately not. It’s 3 days of running since it happened last. I would say it’s almost random.
The most possible is just after (re)boot, there is a case that CPU usage go up when system booted, until ramdisk reset (or use of fsutil usn… command)
1 Like
After 3 years, the problem still persists.
It is clear that Comodo doesn’t care anymore about their customers.
Time to move ahead to other products…
1 Like
I totally confirm!
I was struggling with that cmdagent.exe problem for long time and always was asked for logs, screenshots or whatever they asked. I was surprised because this problem is here for so long and many people reported it, so I can’t understand why they STILL need logs (and more logs, and more logs).
Good programmer should look into code and figure out what is wrong based on sympthoms users described.
But - good news is - after I switched to exFAT for my ImDrive ramdisk, cmdagent.exe no longer eats my resources. I hope it stays that way. But it’s not a solution, it’s workaround (like when you have a car that stops at 3rd gear, so you switch from 2nd to 4th and producer says “well, problem solved!”).
And I know that problem is very old and this topic is old too - but I want to add that I thank you for investigate it and workaround.
1 Like
The problem is they don’t ask for the right type of logs which would be a memory dump of cmdagent when high cpu usage is observed. Also this is not easy to reproduce as I never seem to get high cpu when I tried using ImDisk, even with the real-time AV enabled. It would also help to provide basic steps on how you can cause the issue to occur.
What if basic steps needs whole day of working?
It’s not that cmdagent is utilizing cpu from the beginning. It starts doing it after whole day of working (and not even every day). So I doubt that someone will reproduce 200 steps I made on my PC to reproduce problem.
As I said - symptoms and looking into code for bugs.
1 Like
I get that but if you can pinpoint when it happens it would make it easier to identify what causes it, they can’t just look at the code if they don’t know what part of the code is causing the issue. Does it happen when writing large amount of data to the ram drive? Or does it happen when small but constant read or write access on the ram drive? Can it be replicated if you write a big file or copy/move a large file or large amount of files to or from the ram disk?
Edit: You can also check which thread(s) are using the most CPU that might point to which part of the code that needs to be looked at. Now obviously I’m not getting high CPU so this screenshot doesn’t really matter, but if the start address was within cmdagent itself or a comodo dll, then it should shed a light on what part of the code is trouble.
If they know symptoms and don’t know where to find in code, then I’m very sorry for them. 
Comodo will probably need better programmers.
I am not beta tester, I confirmed when there is CPU high usage, other person too - so it’s now up to Comodo’s programmers to reproduce this issue, not users.
Go back to an earlier build of Comodo and there is no issue with it, or change NTFS to exFAT on the imdisk partitions.
I wouldn’t mind them fixing it, but as long as there are workarounds they can focus on more pressing issues.
You probably don’t know how bugs “works”. It’s not that Comodo detects NTFS and start some “buggy” procedure. Bug can affect everyone - it is easier to replicate when ramdisk is in NTFS format, bu that doesn’t mean is related to NTFS. Somewhere in code some kind infinite loop is activated and is worth to investigate why. Because after some time you’ll realize that if you want to use Comodo Firewall without a problem, you will be forced not only to change NTFS to exFat, but also stop using software XXX or drive letter N:, or using some other tools etc. Error is not intentional so is unpredictable. In this case “focus on more pressing issues” would mean “forget it forever like it happens for many years”.
So you can replicate this issue with exfat?
“So…” at the beginning means you don’t really undersand what I mean.
There is no “so”, I never said I have this issue with exFat, I never said that it’s not working workaround - it is, but we still don’t know why that happens and when it starts behave wrong in other situation. Bug is something that should be found and fixed and people should not must changing strange parameters to made it work.
you don’t really undersand what I mean.
“I have problem A, why can it not get fixed immediately”
- “A is not a critical issue, because there are workarounds, meanwhile they are fixing XYZ”
“but I do not want to use workarounds, and problem A could also have been potential problems BCDEFGHIJKLMNO”
- “Can you confirm that you have any of these BCDEFGHIJKLMNO problems?”
“I want A fixed now.”
Blessed are those who in the 21st century can understand what someone has written, instead of trying to hide their ignorance with irony. BB.
Nah, you’re just needy.
Version 2024 is about to be released… they’ve recruited new programmers and promised to fix all the bugs.
Now’s the last time to report them and air your grievances here: