Sorry, two things:
1. There is no stack trace in this bug. So we can't do anything with it.
2. If it is heap corruption like bug 750386 then we need to find its source.
If you're not game enough to get valgrind working then please do this:
env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace
That will generate a more usable stack trace if and when it crashes.
** This bug is no longer a duplicate of bug 750386
compiz crashed with SIGABRT in raise() from abort() from __libc_message()
from malloc_printerr() from _int_free()
** Changed in: compiz (Ubuntu)
Status: New => Incomplete
** Also affects: compiz
Importance: Undecided
Status: New
** Changed in: compiz
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067820
Title:
compiz crashed with SIGABRT in raise()
To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1067820/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
