** Changed in: mir
    Milestone: None => 0.19.0

** Changed in: mir
       Status: New => In Progress

** Changed in: mir
   Importance: Undecided => High

-- 
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/1523900

Title:
  Buffer leak during repeated mirscreencasts causes server to be killed

Status in Mir:
  In Progress
Status in Mir 0.18 series:
  Triaged
Status in mir package in Ubuntu:
  New

Bug description:
  Nexus 4 running latest stable image -

  current build number: 25
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-12-08 11:53:16
  version version: 25
  version ubuntu: 20151118.2
  version tag: OTA-8
  version device: 20150911
  version custom: 20151118.2

  I'm running the following command to capture a screenshot of a running
  app, the unity shell, the splash screen when apps load etc.

    adb shell mirscreencast -m /var/run/mir_socket  -n1

  I'm doing this in a script, across many hundreds of apps, so I'm doing
  it a lot. I'm seeing my script get wedged fairly often with errors
  such as this one:-

  [1449575031.562843] <ERROR> MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168):
 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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to