chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()

[LAZA]

crashed while loading on youtube.com an video

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 31.0.1650.63-0ubuntu1~20131204.1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic i686
ApportVersion: 2.13.1-0ubuntu2
Architecture: i386
CurrentDesktop: XFCE
Date: Sat Jan 25 15:44:17 2014
Desktop-Session:
 DESKTOP_SESSION = xubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/
DetectedPlugins: (no entry found in the Preferences file)
DiskUsage:
 b'Dateisystem Typ Gr\xc3\xb6\xc3\x9fe Benutzt Verf. Verw% Eingeh\xc3\xa4ngt auf\n/dev/sda1 ext4 14G 5,1G 7,5G 41% /\nnone tmpfs 4,0K 0 4,0K 0% /sys/fs/cgroup\nudev devtmpfs 1,3G 4,0K 1,3G 1% /dev\ntmpfs tmpfs 253M 868K 252M 1% /run\nnone tmpfs 5,0M 0 5,0M 0% /run/lock\nnone tmpfs 1,3G 3,6M 1,3G 1% /run/shm\nnone tmpfs 100M 24K 100M 1% /run/user\n'

 Inodes:
 b'Dateisystem Inodes IBenutzt IFrei IUse% Eingeh\xc3\xa4ngt auf\n/dev/sda1 864K 227K 638K 27% /\nnone 214K 2 214K 1% /sys/fs/cgroup\nudev 210K 456 209K 1% /dev\ntmpfs 214K 406 214K 1% /run\nnone 214K 3 214K 1% /run/lock\nnone 214K 17 214K 1% /run/shm\nnone 214K 20 214K 1% /run/user\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-01-24 (0 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140121.1)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=2320.3.1251821066\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,22\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x80ee\ --gpu-device-id=0xbeef\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
 Segfault happened at: 0xb456ceb7: movl $0x1337,0x0
 PC (0xb456ceb7) ok
 source "$0x1337" 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:
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
 __printf_fphex (fp=0x656d2d61, info=0x6d756964, args=0x2a2d722d) at ../stdio-common/printf_fphex.c:157
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGSEGV in __printf_fphex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

[Apport retracing service (apport)]

StacktraceTop:
 content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang (this=0xb7a4af28) at content/gpu/gpu_watchdog_thread.cc:230
 Run (object=<optimized out>, this=<synthetic pointer>) at ./base/bind_internal.h:134
 MakeItSo (weak_ptr=..., runnable=...) at ./base/bind_internal.h:882
 base::internal::Invoker<1, base::internal::BindState<base::internal::RunnableAdapter<void (content::GpuWatchdogThread::*)()>, void (content::GpuWatchdogThread*), void (base::WeakPtr<content::GpuWatchdogThread>)>, void (content::GpuWatchdogThread*)>::Run(base::internal::BindStateBase*) (base=0xaef01330) at ./base/bind_internal.h:1169
 Run (this=<optimized out>) at ./base/callback.h:396

[Launchpad Janitor (janitor)]

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

[Olivier Tilloy (osomon)]

Closing now as this report wasn’t investigated timely and is now too old to be meaningful.
Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner.