compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x000000000cf63bb0 ***
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Resumed from suspend, 30 seconds later, my session hung. Switched to VT1 and back again, and compiz had crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** compiz: double free or corruption (!prev): 0x000000000cf63bb0 ***
CrashCounter: 1
Date: Thu Oct 6 08:53:03 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
ProcCmdline: compiz --replace
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
__libc_message (do_abort=2, fmt=0x7f20661440d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=3, str=0x7f2066144278 "double free or corruption (!prev)", ptr=<optimized out>) at malloc.c:6283
__GI___libc_free (mem=<optimized out>) at malloc.c:3738
?? () from /usr/lib/
nux::IOpenGLSu
Title: compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x000000000cf63bb0 ***
UpgradeStatus: Upgraded to oneiric on 2011-10-03 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nautilus:1741): Gtk-CRITICAL **: gtk_action_
(nautilus:1741): Gtk-CRITICAL **: gtk_action_
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 #857738, 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.