compiz crashed with SIGSEGV in g_object_unref()

[john.yarger]

picture filled the complete screen while browsing within Chrome, I clicked, and this error was reported...

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CheckboxSubmission: 1b3df9a3df733935b881e50b8e49c7aa
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
CrashCounter: 1
Date: Fri Sep 16 16:27:34 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: compiz --sm-client-id 105dae80e752ea2bb1131536247568485500000014960039
SegvAnalysis:
 Segfault happened at: 0x7f90e13b2ca2 <g_object_unref+18>: mov (%rdi),%rax
 PC (0x7f90e13b2ca2) ok
 source "(%rdi)" (0x100000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 BamfLauncherIcon::~BamfLauncherIcon() () from /usr/lib/compiz/libunityshell.so
 BamfLauncherIcon::~BamfLauncherIcon() () from /usr/lib/compiz/libunityshell.so
 nux::Object::Destroy() () from /usr/lib/libnux-core-1.0.so.0
 nux::Object::UnReference() () from /usr/lib/libnux-core-1.0.so.0
Title: compiz crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to oneiric on 2011-09-15 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #849792, 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.