chromium-browser crashed with SIGSEGV in nouveau_fence_update()

[miguel lopez]

crash opening a flash aplication

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: chromium-browser 13.0.782.215~r97094-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Sun Sep 11 21:23:00 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 amd64 (20110905)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=2238.0x7f2af8bfbd80.316793772
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fe7c7d037ff: mov 0x8(%rbx),%rbp
 PC (0x7fe7c7d037ff) ok
 source "0x8(%rbx)" (0x6c616d7277) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 nouveau_fence_update () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 nv50_default_flush_notify () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 nouveau_pushbuf_flush () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/dri/libgallium.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=""

[Joshua Lückers (joshualuckers)]

I only experience this issue when visiting the website neowin.net.

[dc (darkcharl)]

Have experienced it on a different website

[matt_hargett (matt-use)]

I also experienced it on a different web site. This started happening when I installed the nvidia-current driver (I was testing to see if nouveau was triggering another bug I'm having). I did reboot after installing nvidia-current, so I'm confused as to why Chrome would still be trying to use it somehow.

[dino99 (9d9)]

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