If there's an issue in the transport in
mclr::MirProtobufRpcChannel::send_message during the sending of the
message, it will trigger the disconnection code.
If the client happens to be mid-mir_buffer_stream_swap_buffers at the
same time that the the connection error trips the disconnection
notification, we'll see that error. In the case of a true disconnection,
the only reasonable thing the client code can do is to throw, as it can
no longer appropriately fulfil the mir_buffer_stream_swap_buffers
requirement.
Also, iirc, there are certain things that the client can try to do that
will cause the server to disconnect it, maybe its an issue like that?
** Changed in: mir
Milestone: None => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::exception::what: disconnected: no new buffers" via
ExchangeSemantics::submit()
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
