Comment 5 for bug 1260311

We're tracking that other stack trace pattern from comment #4 in bug 1267364, and are seeing it even on 1.543 (where that issue is supposedly fixed), so either we have a different bug on that one or they didn't fix it/regressed. Anyway, it seems to be unrelated to the stack trace in the bug description so please let's keep these issues separate (they likely have no more in common with one another than two random Python tracebacks would).