I don't think it's sensible to reopen/reuse this old bug for quantal.
Heap corruption can be introduced by any manner of new logic. And the
crash it produces will often have an old-looking call stack like this
one.
Instead we should focus on finding the corruption at its source. To do that,
please run:
env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace
And if/when it crashes, please log a new bug.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/750386
Title:
compiz crashed with SIGABRT in raise() from abort() from
__libc_message() from malloc_printerr() from _int_free()
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/750386/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~compiz
Post to : [email protected]
Unsubscribe : https://launchpad.net/~compiz
More help : https://help.launchpad.net/ListHelp
