compiz crashed with SIGSEGV in intel_miptree_release()

Bug #927720 reported by Martin Mrazik
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

A random compiz crash I've seen. I was in the middle of reporting a bug for sound-indicator (apport-bug /usr/lib/indicator-sound/indicator-sound-service) but I don't if the crash was really initiated by apport. I'll update the bug if I'm able to reproduce.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic-pae 3.2.3
Uname: Linux 3.2.0-14-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Mon Feb 6 17:29:28 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0xb5d81ed5 <intel_miptree_release+21>: mov (%esi),%eax
 PC (0xb5d81ed5) ok
 source "(%esi)" (0x000001a0) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 intel_miptree_release () from /usr/lib/i386-linux-gnu/dri/i965_dri.so
 intel_update_renderbuffers () from /usr/lib/i386-linux-gnu/dri/i965_dri.so
 intelSetTexBuffer2 () from /usr/lib/i386-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
Title: compiz crashed with SIGSEGV in intel_miptree_release()
UpgradeStatus: Upgraded to precise on 2012-01-23 (14 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare

Revision history for this message
Martin Mrazik (mrazik) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 intel_miptree_release (mt=0x1a0) at intel_mipmap_tree.c:290
 intel_process_dri2_buffer_with_separate_stencil (buffer_name=0xb5e12af0 "dri2 hiz buffer", rb=0xa564bd0, buffer=<optimized out>, intel=0x90c7a60, drawable=<optimized out>) at intel_context.c:1267
 intel_update_renderbuffers (context=0x90c5728, drawable=0x9d7d910) at intel_context.c:361
 intelSetTexBuffer2 (pDRICtx=0x90c5728, target=3553, texture_format=8410, dPriv=0x9d7d910) at intel_tex_image.c:335
 dri2_bind_tex_image (dpy=0x9073be8, drawable=17391179, buffer=8414, attrib_list=0x0) at dri2_glx.c:891

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
Revision history for this message
Omer Akram (om26er) wrote :

looks like a driver crash to me.

visibility: private → public
Changed in unity (Ubuntu):
importance: Medium → Critical
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 926379, so it 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. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.