Comment 9 for bug 708243

kyleabaker (kyleabaker) wrote :

While that may serve as a quick fix for alpha and beta testers, it is by no means a solution to the problem.

There is a branch opened for this bug (linked to above), but I've not had time to look into it to see how close it is to solving the problem. A better solution would be to not load duplicate indicators in the first place by possibly using a queue of some sort for initially called indicator items and removing them when they load.