chromium-browser crashed with SIGSEGV (flash/npviewer.bin related)q

[Arthur Peters]

The crash occurs whenever I start playing a flash video on icanhascheezburger.com (I noticed the problem on 2 videos and did not test more). Interesting the image of the page freezes and the video is not rendered but the audio is played until I close the chromium tab.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: chromium-browser 13.0.782.215~r97094-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 3 19:20:01 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:

ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=2422.0x7fa0b42d1480.34276629
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f9e98acd350: mov %eax,0x0
 PC (0x7f9e98acd350) ok
 source "%eax" ok
 destination "0x0" (0x00000000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=""

[Apport retracing service (apport)]

StacktraceTop:
 GpuWatchdogThread::DeliberatelyCrashingToRecoverFromHang() ()
 (anonymous namespace)::TaskClosureAdapter::Run() ()
 MessageLoop::RunTask(MessageLoop::PendingTask const&) ()
 MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask const&) ()
 MessageLoop::DoDelayedWork(base::TimeTicks*) ()

[Arthur Peters (amp)]

A quite look at the stack trace makes me think this may actually be nouveau problem. I am having LOTS of problems with nouveau.

It looks like it was trying to render something via the GLES2 API (gpu::gles2::GLES2DecoderImpl::HandleDrawElements). And the calls to nouveau that resulted from that froze it (nouveau_fence_update).