Comment 5 for bug 376560

I'm going to close this: we've added instrumentation, not seen any recurrences, and its not an active oops in any of our current reports. If it happens again we'll definitely treat it seriously but this bug seems unactionable as it stands.