compiz crashed with SIGSEGV in intel_miptree_release()

[Swarnendu Biswas]

I am using Ubuntu precise. I logged into my system and started synaptic package manager and google chrome when suddenly compiz crashed. I have experienced similar crashes with compiz a few times after immediately logging in.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.2.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 8 18:01:39 2012
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f62d5567d49 <intel_miptree_release+9>: mov (%rdi),%rcx
 PC (0x7f62d5567d49) ok
 source "(%rdi)" (0x00000220) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 intel_miptree_release () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 intel_update_renderbuffers () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 intelSetTexBuffer2 () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 TfpTexture::bindPixmapToTexture(unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so
 boost::detail::function::function_invoker4<GLTexture::List (*)(unsigned long, int, int, int), GLTexture::List, unsigned long, int, int, int>::invoke(boost::detail::function::function_buffer&, unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in intel_miptree_release()
UpgradeStatus: Upgraded to precise on 2012-02-04 (4 days ago)
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 this software better. This particular crash has already been reported and is a duplicate of bug #926379, 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.