Comment 8 for bug 1553328

Done. There doesn't appear to be any way that Mir itself can screw up that call.

It's possible qtmir might be messing up with an incorrect 'this' pointer to the Mir DisplayBuffer. But I think much more likely that it's a nouveau driver bug. If it wasn't then we'd be seeing similar crashes with intel and radeon, but we don't.