compiz crashed with SIGSEGV in ReleaseReference()

[Pixel]

Crash during Dash file preview

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.4.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
Date: Tue Sep 4 18:33:08 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120612)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0xb209a771: mov 0x40(%eax),%eax
 PC (0xb209a771) ok
 source "0x40(%eax)" (0x00000240) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/compiz/libunityshell.so
 unity::glib::Source::SourceCallback(void*) () from /usr/lib/libunity-core-6.0.so.5
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in unity::glib::Source::SourceCallback()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[1805]: WARNING: Application 'compiz.desktop' killed by signal 11
 gnome-session[1805]: WARNING: App 'compiz.desktop' respawning too quickly
 gnome-session[1805]: CRITICAL: We failed, but the fail whale is dead. Sorry....

[Apport retracing service (apport)]

StacktraceTop:
 ReleaseReference (this=0x8e27c48) at /usr/include/Nux-3.0/NuxCore/ObjectPtr.h:329
 Release (this=0x8e27c48) at /usr/include/Nux-3.0/NuxCore/ObjectPtr.h:316
 operator() (this=0x913be38) at /build/buildd/unity-6.4.0/unity-shared/CoverArt.cpp:170
 std::_Function_handler<bool(), unity::dash::previews::CoverArt::StartWaiting()::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/4.6/functional:1764
 operator() (this=<optimized out>) at /usr/include/c++/4.6/functional:2161

[Omer Akram (om26er)]

Thanks for the bug report. This particular bug has already been reported and is a duplicate of bug 1044823, so is being marked as such. Any further discussion regarding the bug should occur in the other report. Feel free to report any other bugs you may find.