compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_unhook()

[Jamie Pocas]

I was watching a video on youtube. I am not sure how to reproduce the crash since this hasn't happened before.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.8.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 25 02:37:00 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8bcaf93270 <_ZNSt8__detail15_List_node_base9_M_unhookEv>: mov (%rdi),%rax
 PC (0x7f8bcaf93270) ok
 source "(%rdi)" (0x292962627375) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 std::__detail::_List_node_base::_M_unhook() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 UnityScreen::getWindowPaintList() () from /usr/lib/compiz/libunityshell.so
 CompositeScreen::getWindowPaintList() () from /usr/lib/compiz/libcomposite.so
 PrivateGLScreen::paintOutputRegion(GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
 GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in std::__detail::_List_node_base::_M_unhook()
UpgradeStatus: Upgraded to oneiric on 2011-08-10 (14 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 #833159, 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.