chromium-browser crashed with SIGSEGV in nouveau_fence_update()

Bug #857795 reported by Matheus Lima de Araújo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

the browser closes when i'm trying to use the angry birds app from the chrome web store.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: chromium-browser 13.0.782.215~r97094-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Sep 23 18:32:46 2011
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=1904.0xb9e7a120.1048113907
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x2dada7ea: mov 0x4(%esi),%edi
 PC (0x2dada7ea) ok
 source "0x4(%esi)" (0x72707363) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
 nouveau_fence_update () from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
 nv50_default_flush_notify () from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
 nouveau_pushbuf_flush () from /usr/lib/i386-linux-gnu/libdrm_nouveau.so.1
 ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
Title: chromium-browser crashed with SIGSEGV in nouveau_fence_update()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Matheus Lima de Araújo (matheusrn89) wrote :
Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and is no more supported

Changed in chromium-browser (Ubuntu):
status: New → Invalid
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.