[mako] Camera-app causing hard reset of device

[Andrew Hayzen]

I've had this 3 times now over the past 6 months, so it doesn't happen very often.

The latest occurrence I was opening the camera-app in photo mode and as the viewfinder was opening the phone reboot instantly with the Google logo, the other occurrences happened when attempting to take a photo. I've been able to extract a log for the latest occurrence here [0]. As you can see from L134 there are Mir/EGL exceptions that happen very rapidly over a short period of time, therefore I'm going to add Mir to this bug as well.

0 - http://pastebin.ubuntu.com/11130346/

$ system-image-cli -i
current build number: 193
device name: mako
channel: ubuntu-touch/devel-proposed-customized-here
alias: ubuntu-touch/vivid-proposed-customized-here
last update: 2015-05-14 13:51:16
version version: 193
version ubuntu: 20150514
version device: 20150210
version custom: mako-1.1

[Alberto Aguirre (albaguirre)]

"std::exception::what: Failed to send message to server: Broken pipe"

The exception messages are just informational messages that are the result of the server process dying (i.e. unity8).

There's no particular evidence that mir is involved in the crash here.

[Daniel van Vugt (vanvugt)]

Mir might still need some improvement tangentially here, because the same error log message appears hundreds of times per second...

[1431536837.289995] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in queueBuffer): /build/buildd/mir-0.12.1+15.04.20150324/src/client/rpc/stream_socket_transport.cpp(154): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"
[1431536837.293261] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in queueBuffer): /build/buildd/mir-0.12.1+15.04.20150324/src/client/rpc/stream_socket_transport.cpp(154): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"
[1431536837.296618] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in queueBuffer): /build/buildd/mir-0.12.1+15.04.20150324/src/client/rpc/stream_socket_transport.cpp(154): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"

[Daniel van Vugt (vanvugt)]

Actually it is possible the server did just die once and libmirclient is too dumb to give up, retrying indefinitely.

[Florian Boucault (fboucault)]

Not much to go on to reproduce :/