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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376324 Title: /usr/sbin/unity-system-compositor:*** Error in `unity-system- compositor': free(): invalid pointer: ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1376324/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
