UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0

Steps to reproduce the problem:
1. Open a terminal and run on the shell: google-chrome
2. Chrome seems to come up but entering anything on the address bar always produces the same result: an unhappy face on the top left of the tab window
3. Not even the about page loads, not even settings

I also tried nuking both config directories:

rm -rf  .config/google-chrome/ .cache/google-chrome/

What I get on my shell:

mcgrof@ergon ~ $ google-chrome
[3581:3618:1025/142627.380616:ERROR:nss_util.cc(725)] After loading Root Certs, loaded==false: NSS error code: -8018
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[3581:3616:1025/142627.770420:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/142627.770583:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[3581:3616:1025/142627.928302:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/142627.928482:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type utility numfds 5 child_pid -1
[3581:3616:1025/142628.944236:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/142628.944357:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[3581:3616:1025/142632.881018:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/142632.881139:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[3581:3616:1025/142727.694027:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/142727.694165:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type utility numfds 5 child_pid -1
[3581:3581:1025/142727.694427:ERROR:web_resource_service.cc(190)] Connection error with the json parser process.
[3581:3616:1025/143017.732594:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/143017.732726:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[3581:3616:1025/143122.107037:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/143122.107182:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[4054:4054:1025/143251.459608:ERROR:ppapi_thread.cc(313)] Failed to load Pepper module from internal-not-yet-present (error: internal-not-yet-present: cannot open shared object file: No such file or directory)
[3581:3616:1025/143251.575878:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/143251.576016:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[3581:3616:1025/143420.370221:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/143420.370353:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[3581:3616:1025/143425.711574:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1025/143425.711726:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1

What is the expected behavior?
google-chrome should let me browse the interwebs.

What went wrong?
Nothing works.

I've attached an image of what it looks like when I try to go to the about page, the first tab is on the chrome://crashes and it also does not load.

Crashed report ID: No, this page does not work

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes 

Chrome version: 63.0.3239.18  Channel: dev
OS Version: openSUSE Tumbleweed 20171010
Flash Version: Not installed

I have checked /var/log/zypp/history for the history of previous versions of chrome to see where this regression occurred. Here is what I can determine:

2017-08-09 11:13:38|install|google-chrome-stable|60.0.3112.90-1|x86_64||google-chrome|179ad66ca11d9a911c4d717b32a7a1565e6570b6|

This one definitely worked.

2017-10-16 13:34:52|install|google-chrome-stable|61.0.3163.100-1|x86_64||google-chrome|344f13736eada714f238ba995635cf55e5e9e959|

This may have been the first release which was affected. It was unclear given I was typically using firefox and I forget if the issue popped up on this release or not.

2017-10-24 08:54:02|install|google-chrome-stable|62.0.3202.62-1|x86_64||google-chrome|14894a418d6f1fb10c2f49d2ed3e1407483a2ce4|

This one *definitely* did not work.

My system is completely up to date:

zypper dup

Ensures my system is up to date. Since my system is up to date I figured I'd try to tackle this issue today. So since stable was not working I figured I'd try beta.

2017-10-25 13:46:34|install|google-chrome-beta|62.0.3202.62-1|x86_64|root@ergon|google-chrome|fd9a716e69186dc8303e879fb506be9841bfc0f8|

Beta did not work either. So I moved to unstable:

2017-10-25 13:54:27|install|google-chrome-unstable|63.0.3239.18-1|x86_64|root@ergon|google-chrome|951b3ac58fa249b32a1ece1d407c7c0d0075751d|

This didn't work either.

I'm a kernel developer at SUSE so we run the latest kernels, figuring it may be an issue with a kernel regression somehow I booted into my old stable kernels, but alas, still the same issue.

Meanwhile, Firefeox works great.
 

Deleted: google-chrome-fails.png 17.6 KB

	google-chrome-fails.png 17.6 KB View Download