Comment 11 for bug 267853

Crash reoccurred. It looks like there are records with intact timestamps that are garbled, so they mis-parse and get converted to error objects with no timestamp. One is attached. Notice at location 4116, right after "Mark D. Meyerson", it looks like the record is truncated and a new one begins. Is it like that in the original logs on pharosdb, i.e. could this be the result of data corruption over the network? I doubt this, but it's possible.