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

Bug #1295699 reported by David Gerard
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

apport

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 32.0.1700.107-0ubuntu1~20140204.977.1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Fri Mar 21 13:51:29 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/
DiskUsage:
 b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda5 ext4 386G 77G 290G 21% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup\nudev devtmpfs 3.9G 12K 3.9G 1% /dev\ntmpfs tmpfs 787M 1.3M 785M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 3.9G 31M 3.9G 1% /run/shm\nnone tmpfs 100M 32K 100M 1% /run/user\n'

 Inodes:
 b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda5 25M 735K 24M 3% /\nnone 983K 2 983K 1% /sys/fs/cgroup\nudev 980K 523 980K 1% /dev\ntmpfs 983K 544 983K 1% /run\nnone 983K 3 983K 1% /run/lock\nnone 983K 35 983K 1% /run/shm\nnone 983K 30 983K 1% /run/user\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2013-03-11 (374 days ago)
InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=1803.16.1850648142\ --disable-gl-multisampling\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,9,23\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0152\ --gpu-driver-vendor=Mesa\ --gpu-driver-version=10.1
SegvAnalysis:
 Segfault happened at: 0x7f0c30d7fb98: movl $0x1337,0x0
 PC (0x7f0c30d7fb98) 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: Upgraded to trusty on 2014-03-05 (16 days ago)
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'

Revision history for this message
David Gerard (dgerard) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
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.