compiz crashed with SIGSEGV in CompPlugin::VTableForScreenAndWindow<unity::UnityScreen, unity::UnityWindow>::finiWindow()

[Cristian Neacsu]

compiz crashed with SIGSEGV in CompPlugin::VTableForScreenAndWindow<unity::UnityScreen, unity::UnityWindow>::finiWindow()

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Feb 19 11:28:13 2012
DuplicateOf: https://bugs.launchpad.net/bugs/931068
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120218)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa7b61303c7 <_ZN10CompPlugin24VTableForScreenAndWindowIN5unity11UnityScreenENS1_11UnityWindowEE10finiWindowEP10CompWindow+23>: mov 0x8(%rdx),%rdx
 PC (0x7fa7b61303c7) ok
 source "0x8(%rdx)" (0xd10014100000035) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 CompPlugin::VTableForScreenAndWindow<unity::UnityScreen, unity::UnityWindow>::finiWindow(CompWindow*) () from /usr/lib/compiz/libunityshell.so
 CompPlugin::windowFiniPlugins(CompWindow*) () from /usr/lib/libcompiz_core.so.ABI-20120216
 CompWindow::~CompWindow() () from /usr/lib/libcompiz_core.so.ABI-20120216
 CompWindow::~CompWindow() () from /usr/lib/libcompiz_core.so.ABI-20120216
 PrivateScreen::removeDestroyed() () from /usr/lib/libcompiz_core.so.ABI-20120216
Title: compiz crashed with SIGSEGV in CompPlugin::VTableForScreenAndWindow<unity::UnityScreen, unity::UnityWindow>::finiWindow()
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 #931068, 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.