compiz crashed with SIGSEGV in std::list<unity::debug::Introspectable*, std::allocator<unity::debug::Introspectable*> >::remove()

[ChemicalKicks]

Can't really provide any additional information, left laptop open while I went to get a bath. Had a few applications open, email, Chromium and empathy etc

When I came back the screen was black but the backlight was on, hit a key, unlocked and was presented with a compiz has crashed error message. so here we are :)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.0.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic i686
ApportVersion: 1.90-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sun Jan 15 20:20:45 2012
DuplicateOf: https://bugs.launchpad.net/bugs/916891
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x1bf3580 <_ZNSt4listIPN5unity5debug14IntrospectableESaIS3_EE6removeERKS3_+48>: cmp %edx,0x8(%esi)
 PC (0x01bf3580) ok
 source "%edx" ok
 destination "0x8(%esi)" (0x00000048) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 std::list<unity::debug::Introspectable*, std::allocator<unity::debug::Introspectable*> >::remove(unity::debug::Introspectable* const&) () from /usr/lib/compiz/libunityshell.so
 unity::debug::Introspectable::~Introspectable() () from /usr/lib/compiz/libunityshell.so
 unity::PanelIndicatorEntryView::~PanelIndicatorEntryView() () from /usr/lib/compiz/libunityshell.so
 unity::PanelIndicatorEntryView::~PanelIndicatorEntryView() () from /usr/lib/compiz/libunityshell.so
 nux::Object::Destroy() () from /usr/lib/libnux-core-2.0.so.0
Title: compiz crashed with SIGSEGV in std::list<unity::debug::Introspectable*, std::allocator<unity::debug::Introspectable*> >::remove()
UpgradeStatus: Upgraded to precise on 2012-01-15 (0 days ago)
UserGroups: admin

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #916891, 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.