chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()

[penalvch]

Was looking at another window while accessing www.optionsxpress.com in Chromium. Crash window appeared, and the tabs with www.optionsxpress.com were found to have disappeared.

WORKAROUND: Open in Firefox.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 34.0.1847.116-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Jul 26 16:23:36 2014
Desktop-Session:
 DESKTOP_SESSION = gnome-fallback-compiz
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-fallback-compiz:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome-fallback-compiz:/usr/share/gnome:/usr/local/share/:/usr/share/
DetectedPlugins:

DiskUsage:
 b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda2 ext4 158G 81G 69G 55% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup\nudev devtmpfs 3.6G 4.0K 3.6G 1% /dev\ntmpfs tmpfs 738M 1.3M 737M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 3.7G 16M 3.6G 1% /run/shm\nnone tmpfs 100M 72K 100M 1% /run/user\n/dev/sda1 vfat 511M 3.4M 508M 1% /boot/efi\n'

 Inodes:
 b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda2 10M 315K 9.7M 4% /\nnone 922K 2 922K 1% /sys/fs/cgroup\nudev 920K 524 919K 1% /dev\ntmpfs 922K 548 922K 1% /run\nnone 922K 3 922K 1% /run/lock\nnone 922K 38 922K 1% /run/shm\nnone 922K 38 922K 1% /run/user\n/dev/sda1 0 0 0 - /boot/efi\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = /usr/lib32
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
ExecutableTimestamp: 1397498973
InstallationDate: Installed on 2014-06-21 (35 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=27714.5.1638107215\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,1,28\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x1002\ --gpu-device-id=0x9830\ --gpu-driver-vendor=ATI\ /\ AMD\ --gpu-driver-version=13.35.10
ProcCwd: /home/moniker
SegvAnalysis:
 Segfault happened at: 0x7fa9130aeb88: movl $0x1337,0x0
 PC (0x7fa9130aeb88) 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
 base::MessageLoop::RunTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
 base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
 base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from /usr/lib/chromium-browser/libs/libbase.so
 ?? () from /usr/lib/chromium-browser/libs/libbase.so
Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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'
modified.conffile..etc.chromium.browser.default: [modified]
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-06-22T09:45:35.603319

[Apport retracing service (apport)]

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 #1229021, 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.