Wow…

Seriously, people. The bug exists at least from April, it has been reported in May, now we have October and it has not been fixed yet???

I only learned about it now, because I upgraded FF only a week ago. And for a week I tried to troubleshoot it on my own until finally I googled that it is Avast’s fault. I immediately updated Avast to the last version and… surprise. The bug is still there.

This is outrageous. And not only because it renders one of the major browsers unusable, but mainly because it seems like there is a serious flaw in the way Avast works. Why? Because turning off shields does not help (sic!). I always thought that when you turn off shields, antivirus programs stop messing with your system. Isn’t it how you diagnose compatibility problems, for Baal’s sake??? Had it worked like it should, I would have troubleshot this bug in 10 minutes. Because of course compatibility with Avast was one of the first things I checked. Instead, I wasted a week, because I chose the antivirus that cannot be trusted - your antivirus. Now I wonder if some other issues with my system are not Avast-related too?

You may ask yourselves why do I bother to write all of this, if I’m not going to use Avast again (I think it is obvious that after this I will move to AVG or Avira)?

Well, I’m simply shocked by the level of your incompetence and I thought I’ll just let you know how lame you are.

Take care,

Antipop