compiz crashed with SIGSEGV in nux::WindowCompositor::RenderTopViews()

[tekstr1der]

This was supposedly fixed, but still seeing the crash on fully updated natty with unity 3.8.4-0ubuntu1

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.40-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 9 14:55:36 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd892cc61e5 <_ZN3nux16WindowCompositor14RenderTopViewsEbRSt4listINS_13ObjectWeakPtrINS_10BaseWindowEEESaIS4_EEbb+101>: mov 0x20(%r13),%rdi
 PC (0x7fd892cc61e5) ok
 source "0x20(%r13)" (0x00000071) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::WindowCompositor::RenderTopViews(bool, std::list<nux::ObjectWeakPtr<nux::BaseWindow>, std::allocator<nux::ObjectWeakPtr<nux::BaseWindow> > >&, bool, bool) () from /usr/lib/libnux-0.9.so.0
 nux::WindowCompositor::Draw(bool, bool) () from /usr/lib/libnux-0.9.so.0
 nux::WindowThread::RenderInterfaceFromForeignCmd(nux::Rect*) () from /usr/lib/libnux-0.9.so.0
 UnityScreen::paintDisplay(CompRegion const&) () from /usr/lib/compiz/libunityshell.so
 UnityWindow::glDraw(GLMatrix const&, GLFragment::Attrib&, CompRegion const&, unsigned int) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in nux::WindowCompositor::RenderTopViews()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev 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 #754461, 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.