touch-packages team mailing list archive

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

Suspicious still. There has been one similar (heap corruption?) crash on Mir 0.10.0 since it got released:
https://errors.ubuntu.com/oops/73fadb24-9ca5-11e4-a40f-fa163e78b027

Not sure what that is because we can't see the full stack trace without it getting grouped under:
https://errors.ubuntu.com/problem/bfb855ebc60f251bf495a2ffb24f2924c50bdbf8
which *might* be a different full stack trace... ?

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

Title:
  /usr/sbin/unity-system-compositor:*** Error in `unity-system-
  compositor': free(): invalid pointer: ADDR ***

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Mir:
  Fix Released
Status in Mir 0.8 series:
  In Progress
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir package in Ubuntu RTM:
  Triaged

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

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