compiz crashed with SIGSEGV in void std::vector<unsigned int, std::allocator<unsigned int> >::_M_insert_aux<unsigned int>()

[sabby7890]

Just crashed when Ubuntu was still loading and I clicked to open Dash twice. For the first time it opened successfully, the second time it just drawn the outline and got frozen.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Sat Sep 22 13:35:00 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 void std::vector<unsigned int, std::allocator<unsigned int> >::_M_insert_aux<unsigned int>(__gnu_cxx::__normal_iterator<unsigned int*, std::vector<unsigned int, std::allocator<unsigned int> > >, unsigned int&&) () from /usr/lib/compiz/libunityshell.so
 std::vector<unsigned int, std::allocator<unsigned int> >::insert(__gnu_cxx::__normal_iterator<unsigned int*, std::vector<unsigned int, std::allocator<unsigned int> > >, unsigned int const&) () from /usr/lib/libunity-core-6.0.so.5
 unity::dash::HomeLens::Impl::LensSearchFinished(std::shared_ptr<unity::dash::Lens> const&) () from /usr/lib/libunity-core-6.0.so.5
 ?? () from /usr/lib/libunity-core-6.0.so.5
Title: compiz crashed with SIGSEGV in void std::vector<unsigned int, std::allocator<unsigned int> >::_M_insert_aux<unsigned int>()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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