Comment 7 for bug 423880

Reading the evidence from this and bug 319173 strongly suggests to me that there is a bug somewhere in Windows XP itself, perhaps in some isolated service pack or other, that causes the problem. See the other bug in particular for the evidence.

As such, I think that there is a very high probability that this is not an OOPS we care about at all.

However, we don't have complete confidence. I'm inclined to gather diagnostic information rather than silencing the OOPS outright. The only diagnostic information I can picture right now is to actually record the attachment, or at least an excerpt of the part of it that fails. That won't close this bug, but it would set us up to close it hopefully the next time it does.

An annoyance in fixing this is that the error happens within standard library and Zope code: any code changes will be monkey patches or custom eggs.