Bug 26177 - Chromium 79 incompatible with glibc 2.31 sandboxing, causes tab and extension crashes
Summary: Chromium 79 incompatible with glibc 2.31 sandboxing, causes tab and extension...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL: https://bugzilla.redhat.com/show_bug....
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-08 21:55 CET by Ralf Brown
Modified: 2020-02-10 07:18 CET (History)
1 user (show)

See Also:
Source RPM: chromium-browser-stable-79.0.3945.130
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ralf Brown 2020-02-08 21:55:09 CET 
Description of problem:
After full update today, Chromium tabs (and the uBlock Origin extension) crash within seconds.

Version-Release number of selected component (if applicable):
glibc-2.31-1, chromium-browser-79.0.3945.130-1

How reproducible:
Open chromium-browser with uBlock Origin installed and/or visit Javascript-heavy sites like Gmail.

Steps to Reproduce:
(1. Open Chromium)
(2. Install uBlock Origin and activate it)
(3. wait a few seconds for the "extension crashed" popup.)
4. Restart Chromium from a shell and visit mail.google.com/mail
5. Wait a few seconds until uBlock (if installed) and tab have crashed
6. see error message on Standard Output:  ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230

To fix:
Upgrade Chromium from upstream (see discussion on linked Redhat bugzilla).
Comment 1 Lewis Smith 2020-02-09 11:05:20 CET 
Thank you for the report, the pointer and the diagnostic.

Our latest version 79.0.3945.130 is actually ready as an M7 security update (bug 26103). I think we should let that go. The circumstance of this bug are obscure.

Assigning to Christiaan as the registered active maintainer for the
chromium-browser-stable SRPM.

@Ralf : When the newer Chromium browser arrives in Cauldron, can *you* please test the specific fault you report here; and report the result.

CC: (none) => lewyssmith
Assignee: bugsquad => cjw
Source RPM: glibc-2.31-1.mga8 chromium-browser-79.0.3945.130-1.mga8 => chromium-browser-stable-79.0.3945.130

Comment 2 Christiaan Welvaart 2020-02-09 14:25:48 CET 
Confirmed: with chromium M79 on glibc 2.31, each tab crashes after a couple of seconds, except in one case all the ads crashed but the page did not. With M80, no crashes so far. Building chromium-browser-stable 80.0.3987.87 for cauldron on the build system will take a couple of hours (and may fail).

Status: NEW => ASSIGNED

Comment 3 Lewis Smith 2020-02-09 21:16:27 CET 
(In reply to Christiaan Welvaart from comment #2)
> Confirmed: with chromium M79 on glibc 2.31, ...
> in one case all the ads crashed but the page did not.
Sounds ideal! A selling point?
Comment 4 Ralf Brown 2020-02-10 07:18:20 CET 
Installed 80.0.3987.87 and have been using it for the past half hour.  Running stable so far, so I think we can mark this issue resolved.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.