touch-packages team mailing list archive

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

It would depend entirely on how much the code touches the heap. In a
reasonably efficient project, the heap (structure not content) doesn't
change that much. You always have to assume malloc/free/new/delete are
slow and should avoid them. So the offending corruption could have
happened some time ago.

-- 
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 Mir:
  Incomplete
Status in Unity System Compositor:
  Incomplete
Status in “mir” package in Ubuntu:
  Incomplete
Status in “unity-system-compositor” package in Ubuntu:
  Incomplete

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/mir/+bug/1376324/+subscriptions