*** This bug is a duplicate of bug 1229021 ***
https://bugs.launchpad.net/bugs/1229021
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.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1303850/+attachment/4072051/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1303850/+attachment/4072054/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1303850/+attachment/4072059/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1303850/+attachment/4072060/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1303850/+attachment/4072061/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1303850/+attachment/4072064/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1303850/+attachment/4072065/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of private bug 1229021
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1303850
Title:
chromium-browser crashed on resume with SIGSEGV in
base::MessageLoop::RunTask()
Status in “chromium-browser” package in Ubuntu:
New
Bug description:
On resume from suspend, system reported Chromium had crashed - never
saw the Chromium window (with my session which had lots of tabs)
again. I had also needed to kill gnome-screensaver to get back to my
login (which is a recurrent separate issue on my 14.04).
Updated to latest as of today and rebooted after upgrade.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 33.0.1750.152-0ubuntu1~pkg995.1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 7 14:36:41 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/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = /usr/lib32
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-02-16 (49 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
ProcCmdline: chromium-browser\ --type=gpu-process\
--channel=2692.18.1361575603\ --supports-dual-gpus=false\
--gpu-driver-bug-workarounds=0,1,27\ --disable-accelerated-video-decode\
--gpu-vendor-id=0x1002\ --gpu-device-id=0x6758\ --gpu-driver-vendor=ATI\ /\
AMD\ --gpu-driver-version=13.35.10
SegvAnalysis:
Segfault happened at: 0x7fa3fddda808: movl $0x1337,0x0
PC (0x7fa3fddda808) 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 staff sudo users
chromium-default: CHROMIUM_FLAGS=""
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'metacity\n'/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.default.chromium.browser: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1303850/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
