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 Desktop
Packages, which is subscribed to xorg-server in 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()
Status in Canonical System Image:
Confirmed
Status in Mir:
Confirmed
Status in mir package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
Under heavy resizing (stress testing under Valgrind), my Mir client
(Xmir) crashed with:
[1444895332.392862] <ERROR> MirBufferStreamAPI: Caught exception at client
library boundary (in mir_buffer_stream_swap_buffers):
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
Throw in function virtual MirWaitHandle*
{anonymous}::ExchangeSemantics::submit(const std::function<void()>&,
mir::geometry::Size, MirPixelFormat, int)
Dynamic exception type:
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
>
std::exception::what: disconnected: no new buffers
The strange thing is it's only the client that died. The server
survived and I can connect new clients to it.
Duplicate bug reports now show Unity8 is another such client suffering
from this crash. It's occurring on phones in the wild.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
