compiz crashed with SIGSEGV in intel_miptree_release()

Bug #932217 reported by Timo Aaltonen on 2012-02-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)

Bug Description

Crashed when I started firefox which tried to launch the previous session. Now after the crash I can see only one firefox window, the others are gone.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Feb 14 19:47:44 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: compiz
 PATH=(custom, user)
 Segfault happened at: 0x7f19a6c5fd59 <intel_miptree_release+9>: mov (%rdi),%rcx
 PC (0x7f19a6c5fd59) 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
 intel_miptree_release () from /usr/lib/x86_64-linux-gnu/dri/
 intel_update_renderbuffers () from /usr/lib/x86_64-linux-gnu/dri/
 intelSetTexBuffer2 () from /usr/lib/x86_64-linux-gnu/dri/
 TfpTexture::bindPixmapToTexture(unsigned long, int, int, int) () from /usr/lib/compiz/
 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/
Title: compiz crashed with SIGSEGV in intel_miptree_release()
UpgradeStatus: Upgraded to precise on 2012-02-10 (4 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild

Timo Aaltonen (tjaalton) wrote :
Timo Aaltonen (tjaalton) wrote :

shutting the firefox session down and restarting it didn't crash compiz again, and I got all the windows back, so they were just inaccessible the first time (not even alt-tab had them)

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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers