Comment 2 for bug 1490603

Revision history for this message
Aaron Bentley (abentley) wrote :

I don't see any instances of the problem since August 28 (build 3016), so I agree this appears to have been solved.