Another duplicate today.
This bug in libmirclient is now causing Untiy8 to fail start-up
sometimes, and black-screen.
** Tags added: black-screen unity8-desktop
** Summary changed:
- libmirclient gives up and terminates prematurely with "std::exception::what:
disconnected: no new buffers" via ExchangeSemantics::submit()
+ unity8/libmirclient gives up and terminates prematurely with
"std::exception::what: disconnected: no new buffers" via
ExchangeSemantics::submit()
** Description changed:
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.
+ ---
+ Duplicate bug reports now show Unity8 is another such client suffering from
this crash. It's occurring on phones and desktops in the wild.
--
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:
unity8/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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
