compiz crashed with SIGSEGV in __dynamic_cast()

[Mark O]

Nothing too strenuous from a compositing point of view - typing in a terminal and the display paused while compiz crashed. Have had similar occurrences before but bug submissions rejected because packages were out of date. I did an update and hour ago so fingers crossed not again.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140220-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Feb 26 05:19:03 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-02-18 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140217)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb75d5a64 <__dynamic_cast+20>: mov -0x8(%eax),%ecx
 PC (0xb75d5a64) ok
 source "-0x8(%eax)" (0xfffffff8) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 __dynamic_cast () from /usr/lib/i386-linux-gnu/libstdc++.so.6
 nux_base_window_accessible_check_active () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in __dynamic_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin macro macro-ops 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 #1283847, 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.