wet_output_handle_destroy failes with assert when disconnecting an output that has a surface/client rendering on that output
wet_output_handle_destroy is being called when the output is being destroyed. It gets passed a wl_listener and a weston_output. There's an assert that tests if that weston_output is the same as wet_output->output. It seems that wet_output->output points to some garbage memory location upon looking at backtrace. Besides the weston_output, struct wet_ouput members seem to point to correct data. That wet_output->output will only get corrupted if there's an active client when (manually) disconnecting the output.