My understanding of the traces: the clients are failing because the server has crashed (or is otherwise unreachable). The problem seems to be that the failure happens in the context of a callback from the Android driver which presumably doesn't handle C++ exceptions well (probably not at all), causing an abort.
My guess about what we need to do is: catch the exception at the Mir/driver glue layer (in MirNativeWindow?) and tell the driver of the failure in the way that it expects it, by returning an error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347053 Title: Clients are crashing with a fatal exception in MirSocketRpcChannel::send_message() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1347053/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
