So, I just got this crash and apport told me it couldn't report it
because this one was already reported, except this one is invalid and
the traceback failed. I'm happy to file a new one if somebody can walk
me through forcing apport to make a new report with a new traceback (and
also happy to be coached on how to ensure a useful traceback can be
created in the event that mine is also broken).
** Changed in: chromium-browser (Ubuntu)
Status: Invalid => Confirmed
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Chad Miller (cmiller)
--
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/1355591
Title:
chromium-browser crashed with SIGSEGV in ShCompile()
Status in “chromium-browser” package in Ubuntu:
Confirmed
Bug description:
Upgrade and crash.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 36.0.1985.125-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
Uname: Linux 3.16.0-7-generic x86_64
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Aug 12 00:02:02 2014
Desktop-Session:
DESKTOP_SESSION = gnome
XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
Disassembly: => 0x0: No se puede acceder a la memoria en la dirección 0x0
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-04-27 (106 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
ProcCmdline: chromium-browser\ --type=gpu-process\
--channel=3586.0.1567776759\ --disable-breakpad\ --supports-dual-gpus=false\
--gpu-driver-bug-workarounds=1,10,14\ --gpu-vendor-id=0x8086\
--gpu-device-id=0x0116\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
Segfault happened at: 0x0: No se puede acceder a la memoria en la
dirección 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
source "0x0" (0x00000000) not located in a known VMA region (needed readable
region)!
SegvReason:
executing NULL VMA
reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
?? ()
?? () from /usr/lib/chromium-browser/libs/libtranslator.so
?? () from /usr/lib/chromium-browser/libs/libtranslator.so
ShCompile () from /usr/lib/chromium-browser/libs/libtranslator.so
gpu::gles2::ShaderTranslator::Translate(char const*) () from
/usr/lib/chromium-browser/libs/libgpu.so
Title: chromium-browser crashed with SIGSEGV in ShCompile()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare 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'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-04-27T17:58:46.529285
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1355591/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp