Comment 21 for bug 145289

I see the upstream bug is sort of DOA (plus it's got a different backtrace than this one so isn't really relevant anyway), however in digging through the source code it appears the _mesa_update_framebuffer() function has been revamped a goodly bit since this trace was taken, so perhaps the issue has been fixed. There's been no other reports of this particular issue so hopefully that means this is a good assumption.