compiz crashed with SIGSEGV in ExtensionPluginAnimAddon::prePaintOutput()

[denk_mal]

Compiz is starting up again and again.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 13 06:51:24 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120228)
ProcCmdline: compiz --replace
ProcEnviron:
 LANGUAGE=de:en
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa17775ac10 <_ZN24ExtensionPluginAnimAddon14prePaintOutputEP10CompOutput+144>: mov 0x8(%rax),%rdi
 PC (0x7fa17775ac10) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ExtensionPluginAnimAddon::prePaintOutput(CompOutput*) () from /usr/lib/compiz/libanimationaddon.so
 PrivateAnimScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libanimation.so
 GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
 PrivateGLScreen::paintOutputs(std::list<CompOutput*, std::allocator<CompOutput*> >&, unsigned int, CompRegion const&) () from /usr/lib/compiz/libopengl.so
 CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so
Title: compiz crashed with SIGSEGV in ExtensionPluginAnimAddon::prePaintOutput()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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