Comment 11 for bug 651134

After approximately 2 days of normal use, the error has not reoccurred (whereas normally we'd see it approximately 3-5 times in a 24 hour period).

I guess we can consider this issue 'gone'.

Cheers.