compiz crashed with SIGSEGV in CompScreen::insertServerWindow()

[Gustavo Guidorizzi]

1) Oneiric 11.10 development
2) compiz:
  Instalado: 1:0.9.5.94+bzr20110919-0ubuntu1
  Candidato: 1:0.9.5.94+bzr20110919-0ubuntu1
  Tabela de versão:
 *** 1:0.9.5.94+bzr20110919-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

3 & 4) I was using Gimp with several windows open when Compiz crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.12.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 26 21:02:43 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x429212 <_ZN10CompScreen18insertServerWindowEP10CompWindowm+306>: mov 0x18(%rax),%rcx
 PC (0x00429212) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 CompScreen::insertServerWindow(CompWindow*, unsigned long) ()
 PrivateWindow::reconfigureXWindow(unsigned int, XWindowChanges*) ()
 CompWindow::configureXWindow(unsigned int, XWindowChanges*) ()
 CompWindow::raise() ()
 PluginAdapter::FocusWindowGroup(std::vector<unsigned long, std::allocator<unsigned long> >) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in CompScreen::insertServerWindow()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin lpadmin 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 #857303, 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.