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

Bug #1351972 reported by penalvch
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Had the browser on http://www.bloomberg.com/news/2014-07-24/german-utilities-bail-out-electric-grid-at-wind-s-mercy.html and all of a sudden, I get an apport window. No user perceptible impact.

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: Wed Jul 30 21:15:57 2014
Desktop-Session:
 DESKTOP_SESSION = None
 XDG_CONFIG_DIRS = None
 XDG_DATA_DIRS = None
DetectedPlugins:

DiskUsage:
 b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda2 ext4 158G 94G 56G 63% /\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 21M 3.6G 1% /run/shm\nnone tmpfs 100M 64K 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 317K 9.7M 4% /\nnone 922K 2 922K 1% /sys/fs/cgroup\nudev 920K 524 919K 1% /dev\ntmpfs 922K 540 922K 1% /run\nnone 922K 3 922K 1% /run/lock\nnone 922K 53 922K 1% /run/shm\nnone 922K 31 922K 1% /run/user\n/dev/sda1 0 0 0 - /boot/efi\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-06-21 (42 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=3059.10.828876721\ --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
SegvAnalysis:
 Segfault happened at: 0x7f88725a5b88: movl $0x1337,0x0
 PC (0x7f88725a5b88) 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

Revision history for this message
penalvch (penalvch) 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.