strange problem after scan

I have been experiencing this “Waiting for cache” freeze problem with Chrome, but you are probably wondering why I am posting this here. For those of you not familiar with details of the problem, any search on the web will probably get you lots of information.

After some detective work I found the problem occurs after a scheduled full system scan with Comodo antivirus. I already tried several suggestions by various folks posted on the web, but none worked. Rebooting the machine resolves the problem, until next scan.

It’s a relatively recent problem affecting my system, and I clued into it having installed CIS about a month ago. To prove this thesis, I scheduled a scan to start just before midnight last night and this morning I woke up to the problem. I am running Windows 8 64 bit. Not sure if anybody has any suggestion about this.

Made a basic paragraph structure for an easier read. Eric

Can you please test it once more and ensure that it does in fact cause this issue. I say this because if it does happen again please create a bug report for this in this section of the forum.

Be sure to use the format provided here and attach both a diagnostics report and the Process List. If you have any questions about how to do any of this please feel free to ask.


When you woke up was the scan by CIS finished? Can the logs tell when it was finished

The reason for asking is that my initial idea was that the problem happened during a CIS scan. But when I read you had a scan run at midnight and the problem persisting in the morning I assumed that the scan had already ended.

You are also referring to a web search that could bring us enlightenment. Could you briefly summarize what a web search could learn us? Are there other reports where scans with other anti virus programs interfere with Chrome?

I have been trying to confirm the problem as suggested by Chiron. I could not find any scan log, which led me to think the scan did not even start. However, it happens every time the “morning after” scheduled scans. I have so far turned off any scheduled scans, and the problem has not happened, but it’s only been a few days.

Is Chrome running when you are scanning or is it closed?

For the purpose of testing. Could you run a quick scan like you would normally run your scheduled scan and see if the problem with Chrome happens again? If it reproduces that makes it an easier test case.