touch-packages team mailing list archive

[Kevin DuBois <kevin.dubois@xxxxxxxxxxxxx>]

seems a race between the mir main EventLoop, and the driver's
notification thread, and the compositing thread. Still on the case,
hampered a bit today by low batteries and slimports not charging the
device

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

Title:
  USC crash on multimonitor unplug

Status in Mir:
  In Progress
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  I've a slightly customized USC built in Silo0. On top of that, a multimonitor-aware unity8 is running.
  http://people.canonical.com/~platform/citrain_dashboard/#?q=ubuntu/landing-000

  On Android devices, Nexus 4 & 7, I occasionally get a crash on
  external monitor unplug. Here is the relevant log:

  ERROR: /build/mir-UAyS26/mir-0.13.4+15.04.20150709.2/src/platforms/android/server/real_hwc_wrapper.cpp(123): Throw in function virtual void mir::graphics::android::RealHwcWrapper::set(const std::array<hwc_display_contents_1*, 3u>&) const
  Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
  std::exception::what: error during hwc prepare(). rc = ffffffff

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