touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Looking at the stack traces, it seems to generally happen on phones when
the screen tries to turn on due to a proximity event from dbus/powerd.

The only reasonable explanation I can find is due to the fact that
MultiThreadedCompositor::start/stop() are not locked. Instead they use
atomic compare/exchange so are written assuming stop/start are called
from the same thread. If stop and start are not called from the same
thread under USC then it's possible we're trying to start the compositor
while it's still stopping. And that might result in us waiting for
incorrect CompositingFunctors.

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

Title:
  unity-system-compositor crashed with std::runtime_error in
  mir::compositor::CompositingFunctor::wait_until_started() from
  usc::MirScreen::set_screen_power_mode (mir_power_mode_on)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  Top crash over past week (ww02) on errors.u.c for rc-proposed
  channels.

  Started with u-s-c 0.2.0+15.04.20151216.1-0ubuntu1

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.2.0+15.04.20151216.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7bcfcf599b35b264c0be45d5290ad9ae3c50adcf
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528384/+subscriptions