Comment 13 for bug 507062

Looking at the stack traces, I'm convinced that bug 458989 and its dupes are not fixed, but duplicates of this bug. 458989 hasn't been closed with an upload, just with an "I do not get this any more", but since this bug happens randomy and there is no known reproducer, it's probably still relevant. Bug 519576 indeed seems like a related, but not identical problem, which was fixed with the referenced upstream patch.