At this point, we have shown a number of users are having the problem. We have shown the it is happening on XP platforms using FF We have shown that it is NOT intermittent
And now we know that it is not just us freebe's, but the same problem is showing up in the purchased product.
Now, I don't work at Avast, but I am a former CTO. If I was the Avast CTO I would get a few computers with configurations that matched those that have reported the problem and set them up to duplicate it. Then I would take a few of my top engineers and look at the changes that were made in the CVS to see what portions of the code that were changed could be generating the defect. This is what you do when you have a baseline that works, and then a release that doesn't. It's not rocket science, it's computer science and it's why we have change control systems. They allow us to see just what was changed to take a working system and make it a broken one.
What is not going to work, for our friend in Canada or for many others, is taking a head in the sand attitude that somehow the changes made to the code are the users fault, and that the failure is on our part.
No anger here, just a deep sense of frustration that it has been over two months and it appears that Avast is saying to us "Too bad, learn to live with it."