compiz crashed with SIGSEGV in brw_upload_state()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu precise (development branch)
Release: 12.04
Architecture: amd64
Compiz version: 1:0.9.7.4-0ubuntu3
Compiz crashed a few seconds after I activated the rain drop effect.
As a result my screen turned black and the only thing left I could do was pushing the reset button on my laptop.
I'm using an old hardware (Thinpad x61 Tablet), that's why I guess that the GPU was overstrained.
You may add a warning or simply automatically turn off effects when it's clear that they need too much hardware resources like e.g. Windows Aero already does it.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 12 20:53:34 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: compiz --sm-client-id 2f53e3fc3-
ProcEnviron:
LANGUAGE=de:en
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fd82a013f1e: mov 0x218(%rax),%rbp
PC (0x7fd82a013f1e) ok
source "0x218(%rax)" (0x00000218) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
brw_upload_state () from /usr/lib/
brw_draw_prims () from /usr/lib/
?? () from /usr/lib/
Title: compiz crashed with SIGSEGV in brw_upload_state()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #947544, 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.