compiz crashed with SIGSEGV in free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The desktop got frozen when I opened a terminal and started a wget process. So I do not think that the action is related to the crash. Something like this happens once a week since I've updated to Ubuntu 11.10
As it happens quite often when I'm using Google Chrome it might be somehow involved in the crash
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Oct 1 20:10:50 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
ProcCmdline: compiz
SegvAnalysis:
Segfault happened at: 0xf9d656: cmp 0xc(%eax),%ecx
PC (0x00f9d656) ok
source "0xc(%eax)" (0xffd2dbeb) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? () from /lib/i386-
free () from /lib/i386-
?? () from /usr/lib/
?? () from /usr/lib/
drm_intel_
Title: compiz crashed with SIGSEGV in free()
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(nautilus:1438): Gtk-CRITICAL **: gtk_action_
(nautilus:1438): Gtk-CRITICAL **: gtk_action_
(process:1477): GdkPixbuf-CRITICAL **: gdk_pixbuf_
(process:1477): GdkPixbuf-CRITICAL **: gdk_pixbuf_
(process:1477): GdkPixbuf-CRITICAL **: gdk_pixbuf_
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 #864446, 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.