Clear browsing history (on exit) causes a delay on exit

Specific symptoms of the bug and steps you can take to reproduce it (step by step). go to dragon settings and enable “clear browsing history” on exit. When you close dragon it takes a couple seconds for it to close.
Specific steps you have taken to try to resolve it. Disable this option fixes the problem
Comodo Dragon Version (Stable/Beta) e.g. Dragon (Beta); e.g. Dragon (Stable)
Plugins/Themes installed in Comodo Dragon v25.2 stable, reproduced with no extensions.
Windows version (w/ 32 or 64-bit) e.g: Windows 7 Ultimate (64-bit); Windows XP SP 3 (32-bit)
UAC status (diabled/enabled) if it applies to you [ for Vista/Windows 7 only! ] Windows 7 ultimate 32 bit, sp1, UAC disabled
System Drive where Windows is installed (e.g. C:, “C” Drive )
Place (installation path) where Comodo Dragon is installed C:
User privileges (administrator, limited user, guest, etc.) Admin
If you have Google Chrome installed then please mention it’s version and whether the same issue reproduces with it. Dont have it installed

Note: Maybe dragon can close instantly then clear the history in the background instead of trying to clear it then exit.

Thanks wasgij6,
I confirm this issue, it is also present on my system.

still present in 26.0.2

not fixed in 27.1

I have also noticed this in

I do not see a long delay but I am seeing what I would call a “hesitation.”

Also, if you clear the browsing history more than once in a period of time the system is popping up a suggestion to use incognito browsing instead.

For a while I was concerned that CD was tracking web visits but that made no sense and it appears to be something that is popping up after a couple of manual cache clears. Rather disturbing at first especially after going in and out of my online banking site a couple of times, and wanting to clear the cache manually.

still not fixed in v28

Any feedback from comodo would be greatly appreciated.


Clearing the data on exit requires the dragon.exe process to remain active for a short time before closing. There are no other feasible methods of deleting that data so this flow will be consistent in future builds.

The idea of closing the Dragon window and leaving only the process running while the data is deleted is being taken into consideration. This should give it a more responsive feel while not affecting performance.


Thanks. Please do consider implementing a fix for this delay. CD is the only program I am aware of that exhibits this behavior, and it is quite disconcerting. Perhaps you could spawn a separate background process to accomplish the data-clearing.