← Back to team overview

touch-packages team mailing list archive

[Bug 1346952] Re: [qtcomp] Random crash in Mir input when running AP tests: [terminate called after throwing an instance of '...' what(): assign: File exists] when constructing a mir::AsioMainLoop::FDHandler

 

This bug was fixed in the package mir - 0.5.1+14.10.20140728-0ubuntu1

---------------
mir (0.5.1+14.10.20140728-0ubuntu1) utopic; urgency=medium

  [ Kevin Gunn ]
  * Fixed: Crash due to racing input registration & surface removal
    (LP: #1346952)

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Mon, 28 Jul 2014 02:49:50 +0000

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

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

Title:
  [qtcomp] Random crash in Mir input when running AP tests: [terminate
  called after throwing an instance of '...' what(): assign: File
  exists] when constructing a mir::AsioMainLoop::FDHandler

Status in Mir:
  Fix Committed
Status in Mir 0.5 series:
  Fix Committed
Status in Qt integration with the Mir display server:
  Invalid
Status in “mir” package in Ubuntu:
  Fix Released

Bug description:
  Steps to repro:
  1. Install QtCompositor - right now from silo6, see https://wiki.ubuntu.com/Unity8/QtComp
  2. Use https://wiki.ubuntu.com/Touch/Testing to get your device set up for running an autopilot test. That can be summarized roughly into running these commands on your PC:

      phablet-config edges-intro --disable
      adb shell powerd-cli display on bright &    #keeps the display on

  3. Run an AP test. This one tends to expose the bug easily:
       phablet-test-run -p ubuntu-html5-ui-toolkit-autopilot ubuntu_html5_ui_toolkit

  The crash we get has this stack trace:
  http://paste.ubuntu.com/7836063/

  "terminate called after throwing an instance of 
  'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  assign: File exists"

  Which points onto the constructor of
  boost::asio::posix::basic_stream_descriptor which in case of the
  default epoll reactor will call epoll_ctl to add the given file
  descriptor. The error number EEXIST indicates that the file descriptor
  is already inside the set.

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