compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0xb6e37ff4 ***

[Andrew Tonks]

oneiric/unity. completely up to date a few hours ago.

Windows stopped responding to mouse clicks, and this crash notification a few seconds later

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.16.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4
Uname: Linux 3.0.0-11-generic-pae i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
AssertionMessage: *** glibc detected *** compiz: free(): invalid pointer: 0xb6e37ff4 ***
Date: Sun Sep 18 10:12:53 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity
StacktraceTop:
 __libc_message (do_abort=2, fmt=0xb6dfd080 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0xb6e37ff4) at malloc.c:6283
 _int_free (av=0xb6e39400, p=0xb6e37fec) at malloc.c:4795
 __GI___libc_free (mem=0xb6e37ff4) at malloc.c:3738
 XFree () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0xb6e37ff4 ***
UpgradeStatus: Upgraded to oneiric on 2011-09-09 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare vboxusers
XsessionErrors:
 (firefox-trunk:2991): Gtk-CRITICAL **: IA__gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed
 (firefox-trunk:2991): Gdk-CRITICAL **: IA__gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #750386, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.