compiz crashed with SIGSEGV in operator[]()

[christopherbalz]

I was typing in the search box of Ubuntu's "Dash Home", the main ubuntu finder search box.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.18.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
Uname: Linux 3.2.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
CrashCounter: 1
Date: Sat Jul 6 10:45:01 2013
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f679534c57e: mov 0x8(%rsi),%rax
 PC (0x7f679534c57e) ok
 source "0x8(%rsi)" (0x10000000a) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tomcat6 video

[Apport retracing service (apport)]

StacktraceTop:
 operator[] (__k=..., this=0x4e0) at /usr/include/c++/4.6/bits/stl_map.h:466
 unity::dash::FilterMultiRangeButton::Draw (this=0x0, GfxContext=..., force_draw=<optimized out>) at /build/buildd/unity-5.20.0/plugins/unityshell/src/FilterMultiRangeButton.cpp:242
 ?? ()
 programArgc () from /tmp/apport_sandbox_FB2xcO/usr/lib/libcompiz_core.so.ABI-20120305
 main (argc=<optimized out>, argv=0x0) at /build/buildd/compiz-0.9.7.12/src/main.cpp:234

[Stephen M. Webb (bregma)]

Stack trace show a signal raised on an invalid object, but unfortunately there is just not enough additional information to perform an effective analysis of this problem. Closing bug since further investigation and resolution is no longer possible.