Comment 16 for bug 634701

I can reproduce this using the appmenus File->Quit every time. It seems to happen because the window is sent a close event outside of Mutter knowing about it and that leaves mutter in a bad state. It ends up getting a bad window error and then calls abort () because of that (which might be a bit too harsh, in this case).