[trusty] [regression] chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()

Bug #1471645 reported by Daniel Richard G. on 2015-07-06
62
This bug affects 8 people
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
Medium
Unassigned
chromium-browser (Ubuntu)
Medium
Unassigned

Bug Description

This bug report concerns chromium-browser version 43.0.2357.81-0ubuntu0.14.04.1.1089 in Ubuntu Trusty.

Previously, this system had 41.0.2272.76-0ubuntu0.14.04.1.1076 installed, and it worked correctly. Now, after an update, the browser crashes immediately upon startup with a SIGABRT. Removing ~/.config/chromium/ and ~/.cache/chromium/ does not alleviate the problem.

If run in a terminal, the program produces the following output:

    [8622:8622:0704/015859:FATAL:zygote_host_impl_linux.cc(182)] Check failed: process.IsValid(). Failed to launch zygote process
    Aborted (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089
ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic i686
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
CrashCounter: 1
Date: Sun Jul 5 23:47:06 2015
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
 '/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share'
DetectedPlugins:

Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-10-23 (256 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
InstalledPlugins:

Load-Avg-1min: 0.44
Load-Processes-Running-Percent: 0.4%
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 23739XU
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdline: chromium-browser\ --enable-pinch\ https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+filebug/aabe74b8-2391-11e5-ad47-d485646cd9a4?field.title=chromium-browser+crashed+with+SIGABRT+in+base%3A%3Adebug%3A%3ABreakDebugger%28%29
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic root=UUID=81f5e3b1-d5da-479e-93bd-d7e6b89cff95 ro forcepae
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
 base::debug::BreakDebugger() () from /usr/lib/chromium-browser/libs/libbase.so
 logging::LogMessage::~LogMessage() () from /usr/lib/chromium-browser/libs/libbase.so
 content::ZygoteHostImpl::Init(std::string const&) () from /usr/lib/chromium-browser/libs/libcontent.so
 content::BrowserMainLoop::EarlyInitialization() () from /usr/lib/chromium-browser/libs/libcontent.so
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
Title: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/14/2004
dmi.bios.vendor: IBM
dmi.bios.version: 1RETC6WW (3.05a)
dmi.board.name: 23739XU
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1RETC6WW(3.05a):bd05/14/2004:svnIBM:pn23739XU:pvrThinkPadT42:rvnIBM:rn23739XU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 23739XU
dmi.product.version: ThinkPad T42
dmi.sys.vendor: IBM
gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/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]

Daniel Richard G. (skunk) wrote :

StacktraceTop:
 base::debug::BreakDebugger () at ../../base/debug/debugger_posix.cc:241
 logging::LogMessage::~LogMessage (this=0xbfb0235c, __in_chrg=<optimized out>) at ../../base/logging.cc:639
 content::ZygoteHostImpl::Init (this=0xb7d74d48, sandbox_cmd=...) at ../../content/browser/zygote_host/zygote_host_impl_linux.cc:182
 SetupSandbox (parsed_command_line=...) at ../../content/browser/browser_main_loop.cc:178
 content::BrowserMainLoop::EarlyInitialization (this=0xb7d74ae8) at ../../content/browser/browser_main_loop.cc:396

Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Daniel Richard G. (skunk) wrote :

The crash is due to AppArmor. Adding the following to the profile for /usr/lib/chromium-browser/chromium-browser gets things working again:

    capability sys_admin,
    capability sys_chroot,

    owner @{PROC}/[0-9]*/setgroups w,
    owner @{PROC}/[0-9]*/gid_map w,
    owner @{PROC}/[0-9]*/uid_map w,

    @{PROC}/[0-9]*/stat r,

Changed in chromium-browser (Ubuntu):
status: New → Invalid
information type: Private → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apparmor (Ubuntu):
status: New → Confirmed
cooloutac (cooloutac) wrote :

I have the same problem on Lubuntu 15.04. Firefox profile works but chromium does not.

Adding the suggested lines to the usr.bin.chromium-profile do not help.

[3622:3622:0912/215938:FATAL:zygote_host_impl_linux.cc(182)] Check failed: process.IsValid(). Failed to launch zygote process
Aborted (core dumped)

cooloutac (cooloutac) wrote :

sorry it actually fixed the issue, this time i downloaded the profile from github and added the lines to the top, before i added them towards the bottom. Thankyou.

tags: added: wily
Changed in apparmor (Ubuntu):
importance: Undecided → Medium
Chad Miller (cmiller) wrote :

Please paste the output of this run in a Terminal.

dpkg -S $(grep -l /etc/apparmor.d/*)

Changed in apparmor (Ubuntu):
status: Confirmed → Incomplete
Daniel Richard G. (skunk) wrote :

Chad, what is the intended purpose of that command? Because it's mistranscribed:

    $ dpkg -S $(grep -l /etc/apparmor.d/*)
    grep: /etc/apparmor.d/apache2.d: Is a directory
    grep: /etc/apparmor.d/cache: Is a directory
    grep: /etc/apparmor.d/disable: Is a directory
    grep: /etc/apparmor.d/force-complain: Is a directory
    grep: /etc/apparmor.d/local: Is a directory
    grep: /etc/apparmor.d/program-chunks: Is a directory
    grep: /etc/apparmor.d/tunables: Is a directory
    dpkg-query: error: --search needs at least one file name pattern argument

    Use --help for help about querying packages.

Do you want to know which package owns the Chromium profile?

    $ dpkg -S /etc/apparmor.d/usr.bin.chromium-browser
    apparmor-profiles: /etc/apparmor.d/usr.bin.chromium-browser

Changed in apparmor (Ubuntu):
status: Incomplete → Confirmed
hda_launchpad (hda-me) wrote :

This should be fixed, but fixed wisely. Consider this first: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1447345

tags: added: xenial
Daniel Richard G. (skunk) wrote :

Chromium continues to fail on Xenial with the title error message when the currently-shipped AppArmor profile is enforced.

I've updated my profile adjustments to address some new issues that have cropped up in recent builds of Chromium.

Everyone who wants to get things working again, please add the following lines to /etc/apparmor.d/local/usr.bin.chromium-browser :

# From https://bugs.launchpad.net/bugs/1471645

#include <abstractions/dbus>

capability sys_admin,
capability sys_chroot,
capability sys_ptrace,

owner @{PROC}/[0-9]*/setgroups w,
owner @{PROC}/[0-9]*/gid_map w,
owner @{PROC}/[0-9]*/uid_map w,

@{PROC}/[0-9]*/stat r,
@{PROC}/sys/net/ipv4/tcp_fastopen r,

/bin/which ixr,

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers