compiz team mailing list archive

[Daniel van Vugt <vanvugt@xxxxxxxxx>]

Unfortunately, any crash in malloc() is not actually a bug in malloc.
Rather, it means the heap was corrupted earlier somewhere else in the
compiz process (probably in the Unity plugin).

In order to trap the root causes of such heap corruption, the program
(compiz) would need to be started with the environment variable
MALLOC_CHECK_=2 (see "man malloc" for documentation).

If you are still able to reproduce this crash, then please reply and let
us know so that we can work with you to enable the debugging option and
pinpoint the cause. If you can't reproduce this crash then nothing more
needs to be done. The bug will expire automatically.

** Project changed: compiz => compiz-core

** Changed in: compiz-core
       Status: New => Incomplete

** Changed in: unity
       Status: Invalid => Incomplete

** Changed in: compiz (Ubuntu)
       Status: New => Incomplete

-- 
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/767963

Title:
  compiz crashed with SIGSEGV in malloc()

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz-core/+bug/767963/+subscriptions