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

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

Bug Description

No idea what happened.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 35.0.1916.153-0ubuntu1~pkg1029
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Aug 8 14:36:16 2014
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
DiskUsage:
 b'Dateisystem Typ Gr\xc3\xb6\xc3\x9fe Benutzt Verf. Verw% Eingeh\xc3\xa4ngt auf\n/dev/sda5 ext4 98G 73G 21G 79% /\nnone tmpfs 4,0K 0 4,0K 0% /sys/fs/cgroup\nudev devtmpfs 3,9G 4,0K 3,9G 1% /dev\ntmpfs tmpfs 788M 1,2M 787M 1% /run\nnone tmpfs 5,0M 4,0K 5,0M 1% /run/lock\nnone tmpfs 3,9G 18M 3,9G 1% /run/shm\nnone tmpfs 100M 60K 100M 1% /run/user\n'

 Inodes:
 b'Dateisystem Inodes IBenutzt IFrei IUse% Eingeh\xc3\xa4ngt auf\n/dev/sda5 6,3M 464K 5,8M 8% /\nnone 984K 4 984K 1% /sys/fs/cgroup\nudev 974K 544 973K 1% /dev\ntmpfs 984K 599 984K 1% /run\nnone 984K 7 984K 1% /run/lock\nnone 984K 42 984K 1% /run/shm\nnone 984K 39 984K 1% /run/user\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2013-12-22 (229 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=19420.0.1201971480\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,9,13\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0126\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
 Segfault happened at: 0x7f3009a22f38: movl $0x1337,0x0
 PC (0x7f3009a22f38) 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 autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-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''/desktop/gnome/interface/gtk_theme = b''
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-07-28T09:39:35.779568

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