Comment 1 for bug 1035308

We get these a lot also, but we just tolerate them. But you're right, we need to either fix it or stop having it raise an alarm.

I'm assigning to Carlos but not until next week. I hope to get a full traceback from the next time it happens. Of course, our inability to get the source file producing this problem is an issue. We might have to put something in place that captures the offending file and copies it to var for analysis.