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.
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} ::ExchangeSeman tics::submit( const std::function< void()> &, mir::geometry: :Size, MirPixelFormat, int) exception_ detail: :clone_ impl<boost: :exception_ detail: :error_ info_injector< std::runtime_ error> > :what: disconnected: no new buffers
Dynamic exception type: boost::
std::exception:
The strange thing is it's only the client that died. The server survived and I can connect new clients to it.