Mir

  1. Bug #1353867
  2. Comment #0

Comment 0 for bug 1353867

Revision history for this message
Daniel van Vugt (vanvugt) wrote : [regression] Nexus4: Mir server gets caught in an infinite exception loop on wakeup ("Caught exception at Mir/EGL driver boundary")

Nexus4: Mir server gets caught in an infinite exception loop on wakeup ("Caught exception at Mir/EGL driver boundary")

Test case:
   1. mir_demo_server_shell
   2. mir_demo_client_egltriangle
   3. Press the power button to sleep
   4. Press the power button again to wake up

Expected: Rendering continues on screen after wakeup
Observed:

Caught exception at Mir/EGL driver boundary: /home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_data(const std::vector<unsigned char>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorEEEEE
std::exception::what: Failed to send message to server: Bad file descriptor
9, "Bad file descriptor"
Caught exception at Mir/EGL driver boundary: /home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_data(const std::vector<unsigned char>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorEEEEE
std::exception::what: Failed to send message to server: Bad file descriptor
9, "Bad file descriptor"
Caught exception at Mir/EGL driver boundary: /home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_data(const std::vector<unsigned char>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorEEEEE
std::exception::what: Failed to send message to server: Bad file descriptor
9, "Bad file descriptor"
.....