Comment 2 for bug 960784

So this is horribly meta: the culprit file is itself reporting a unicodedecode error. I wonder if we have some metabug that leads to bad bson ? That would be a bson encoding error on the server side though, vs an oops bug.

I'm going to mark this low and attach the oops file, if it happens again or we can determine a cause, we can tackle at root. I'm uncomfortable just catching this exception for now.