...I can't speculate as to what will happen once this bug finally gets squashed.
This "bug" as you call it has been in place now for a number of versions and Avast have been aware of it for quite a long time, including right through the last beta.
On the one hand, it doesn't really affect the ability of the software to do it's core task, and if it had only appeared in one version or release would have been of minor importance.
But because it has dragged on for so long, it has assumed much greater significance. One has only to look at the number of posts it keeps turning up in.
If it is just a "bug" then one has to wonder why it has taken so long without a resolution of the issue. Is it in fact a structural design shortcoming that would require a significant amount of recoding to resolve, and hence is being put on the back burner?
Whatever the actual cause it is a quality control issue that now reflects badly on the quality of the product and its developers.