compiz crashed with SIGSEGV in CompWindow::~CompWindow()

[Victor Costan]

I rebooted my computer after having it updated last night, and I got this crash while using Update Manager to do another round of updates. 3-4 crashes came out of that, so I'm not sure if this bug is caused by Update Manager, or by apport while reporting another bug.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: compiz-core 1:0.9.5.94+bzr20110919-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,imgpng,grid,move,place,mousepoll,gnomecompat,vpswitch,snap,regex,session,unitymtgrabhandles,animation,wall,expo,fade,ezoom,scale,workarounds,unityshell]
CompositorRunning: compiz
Date: Sat Sep 24 02:37:55 2011
DistUpgraded: Log time: 2011-09-22 01:31:59.010493
DistroCodename: oneiric
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 8.881, 2.6.38-11-generic, x86_64: installed
 fglrx, 8.881, 3.0.0-11-generic, x86_64: installed
 virtualbox, 4.1.2, 2.6.38-11-generic, x86_64: installed
 virtualbox, 4.1.2, 3.0.0-11-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 ATI Technologies Inc Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller])
   Subsystem: ATI Technologies Inc Device [1002:00d0]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
JockeyStatus:
 kmod:fglrx - ATI Fire GL (Proprietary, Disabled, Not in use)
 xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use)
MachineType: Shuttle Inc. SX58
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=a0d08fc9-3f21-4e85-ba39-635d97e0ee88 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x44403a <_ZN10CompWindowD2Ev+698>: mov 0x20(%rax),%r12
 PC (0x0044403a) ok
 source "0x20(%rax)" (0x00000045) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 CompWindow::~CompWindow() ()
 CompWindow::~CompWindow() ()
 PrivateScreen::removeDestroyed() ()
 PrivateScreen::processEvents() ()
 CompEventSource::callback() ()
Title: compiz crashed with SIGSEGV in CompWindow::~CompWindow()
UpgradeStatus: Upgraded to oneiric on 2011-09-22 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SX58
dmi.board.vendor: Shuttle Inc.
dmi.board.version: V10
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Intel
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd03/30/2011:svnShuttleInc.:pnSX58:pvrV10:rvnShuttleInc.:rnSX58:rvrV10:cvnIntel:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: SX58
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc.
version.compiz: compiz 1:0.9.5.94+bzr20110919-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs 20090808ubuntu23
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

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