← Back to team overview

touch-packages team mailing list archive

[Bug 1353867] Re: [regression] Mir clients get caught in an infinite exception loop when the server goes away ("Caught exception at Mir/EGL driver boundary")

 

** Also affects: mir (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

** Changed in: mir (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1353867

Title:
  [regression] Mir clients get caught in an infinite exception loop when
  the server goes away ("Caught exception at Mir/EGL driver boundary")

Status in Mir:
  Fix Committed
Status in Mir 0.6 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Nexus4: Mir client gets caught in an infinite exception loop if the
  server crashes ("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"
  .....

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1353867/+subscriptions