Actually I just hit a similar exception in a nested server (which throws continuously and infinitely):
[2016-10-05 15:49:42.260127] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): Dynamic exception type: std::logic_error std::exception::what: state was not valid [2016-10-05 15:49:42.262044] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): Dynamic exception type: std::logic_error std::exception::what: state was not valid [2016-10-05 15:49:42.264824] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): Dynamic exception type: std::logic_error std::exception::what: state was not valid [2016-10-05 15:49:42.266636] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): Dynamic exception type: std::logic_error std::exception::what: state was not valid [2016-10-05 15:49:42.269473] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): Dynamic exception type: std::logic_error std::exception::what: state was not valid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630230 Title: Mir crashes from time to time when using Telegram while network changes [AndroidWindow: Caught exception at Mir/EGL driver boundary (in dequeueBuffer): Dynamic exception type: St11logic_error std::exception::what: state was not valid] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1630230/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
