Any crash in malloc() or new() means the process' heap was corrupted
before then. And the source of the heap corruption is therefore not
going to be visible in the stack or traceable once the crash occurs.
I believe (almost) all the sources of key corruption were eliminated in
the unity 5.12 update. So let this bug be incomplete unless the problem
persists...
** Changed in: nux
Status: New => Incomplete
** Changed in: unity
Status: New => Incomplete
** Changed in: nux (Ubuntu)
Status: New => Incomplete
** Changed in: nux (Ubuntu Precise)
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/922178
Title:
compiz crashed with SIGSEGV in _int_malloc()
To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/922178/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
