This may be caused by several things, e.g. broken IPv6 in your network or some
incompatible SW you have installed (e.g. Cisco AnyConnect Web Security Module),
but without any useful info, it is hard to say more.
Well, maybe looking into the system log, before starting blindly restarting your machine
would not be a bad idea…
We do, of course, test our software, before we release it. But it is not possible to test it in
all environments, that may occur on several hundred thousands of machines.
Tumic, this reply was not very helpful. After I read it, I opened Avast and looked on every menu for access to any kind of system log, etc. Nothing there. So if I were to check the system logs, how would I do that? How would I know I needed to do that?
If you mean the full Mac system log – which I’ve seen on a different Mac that started crashing a while back – it’s not like a layman can make sense of all those strings.
When Avast simply starts blocking all but two websites in the entire Internet, maybe it should provide an error message.
Yes, I mean the system log, not any avast log (that does not exists as all avast daemons use
the system log). OS X has a user friendly application for working with the system log called
“Console”. If you have any troubles with your Mac, it is the right place to start with.
Avast does provide such error message, it is written into the system log.