Ubuntu
camera-app package

[mako] Camera-app causing hard reset of device

Bug #1455087 reported by Andrew Hayzen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Invalid
Undecided
Unassigned
camera-app
New
Undecided
Unassigned
camera-app (Ubuntu)
New
Undecided
Unassigned

Bug Description

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

Revision history for this message
Alberto Aguirre (albaguirre) wrote :

"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.

Changed in mir:
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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"

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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

Revision history for this message
Florian Boucault (fboucault) wrote :

Not much to go on to reproduce :/

Daniel van Vugt (vanvugt)
Changed in mir:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.