@vanvugt I try to produce a better crash report but it is difficult because when unity/compiz crash you don't windows borders for move windows and pressing keys for write doesn't write anything.
So, I boot the pc. Enter in a lightdm session. Then I open a terminal. I fire up google-chrome. Then unity crash. I go to tty with Alt+F1 and I write in terminal: DISPLAY=:0 metacity --replace This give me again windows border and keyboard write access pressing Alt+F7. Then I write: env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace > unity-replace2.log Unity crash. I did the same but from tty, and save the output in unity- replace.log. I attach the logs and .xsession-errors that seems have a memory-map and backtrace. ** Attachment added: ".xession-errors" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/750386/+attachment/3379712/+files/.xsession-errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
