Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1773346 - Chromium (and GChrome stable, beta and unstable) crash when visiting any resource-intensive site
Summary: Chromium (and GChrome stable, beta and unstable) crash when visiting any reso...
Keywords:
Status: CLOSED DUPLICATE of bug 1773289
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-17 19:25 UTC by Nicholas Hubbard
Modified: 2019-11-17 21:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-17 21:54:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Nicholas Hubbard 2019-11-17 19:25:24 UTC 
Description of problem:
When visiting any website that uses any kind of resources (CPU, GPU, RAM, etc.) for rendering, the web browser crashes and throws an error in the console, displaying the "Aw, Snap!" error in-window. 

Version-Release number of selected component (if applicable):
chromium: 78.0.3904.97-1.fc32.x86_64
google-chrome-stable: 78.0.3904.97-1.x86_64
google-chrome-beta: 79.0.3945.36-1.x86_64
google-chrome-unstable: 80.0.3964.0-1.x86_64
kernel: 5.4.0-0.rc7.git1.2.fc32.x86_64

How reproducible:
Reproducible in a blank profile (tested on all three browsers) on the kernel version supplied.

Steps to Reproduce:
1. Install any of the above browsers (chromium from rawhide, google-chrome-* from Google's repository)
2. Visit any website which loads actual resources like images, scripts, or styles (I tried Gmail, Reddit, Phoronix, LWN, and many other webpages)
3. Observe the result in the console of a crash

Actual results:
tracing_service_impl.cc: Configured tracing, #sources:3, duration:0 ms, #buffers:1, total buffer size:25600 KB, total sessions:1
[21305:21305:1117/141541.854340:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
tracing_service_impl.cc: Tracing session 1 ended, total sessions:0
tracing_service_impl.cc: Configured tracing, #sources:3, duration:0 ms, #buffers:1, total buffer size:25600 KB, total sessions:1
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230

Expected results:
Webpages load correctly and work immediately after loading

Additional info:
There is an Asciinema recording available at https://asciinema.org/a/MQ9pwezf4JFqg2dlrJRQf4vja. Note: the moment that the crash occurs, I was in the Chrome window visiting a URL which I knew would trigger the crash.
Comment 1 Nicholas Hubbard 2019-11-17 19:28:22 UTC 
My apologies, the Asciinema link was set to private. I made the cast public, and the new URL is https://asciinema.org/a/281952.
Comment 2 Tom "spot" Callaway 2019-11-17 21:54:24 UTC 

*** This bug has been marked as a duplicate of bug 1773289 ***
Note You need to log in before you can comment on or make changes to this bug.