Code review comment for lp:~kdub/mir/compositor-double-start-stop

I'd expect multiple calls to ::MultiThreadedCompositor::start() to be a precondition violation.

Do we really need to handle what sounds like a bug in unity-mir?

If so, is ignoring it really better than aborting?