Comment 10 for bug 1195089

I think there is a good chance that this is fixed now . I'm unable to reproduce it so far. I think the changes in focus control flow in client-focus-notifications fix the main issue that I was seeing (an invalid surface exception is thrown out of focus and handled up in the frontend, preventing the session mediator from clearing it's .session after disconnect and before ~SessionMediator which then tries to destroy the session again but it's gone).