UserAgent: Mozilla/5.0 (Windows NT 6.1; rv:45.0) Gecko/20100101 Firefox/45.0

Steps to reproduce the problem:
1. Enable core dumps in bash: ulimit -Hc unlimited && ulimit -Sc unlimited
2. Start Google Chrome
3. Wait for about a minute after the browser opens

What is the expected behavior?
Chrome should not close unexpectedly.

What went wrong?
All tabs and windows are closed by SIGSEGV (core dumped), no crash report generated.

Crashed report ID: No.

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 55.0.2883.75 (Official Build) (64-bit)  Channel: stable
OS Version: Scientific Linux 7.0 (Nitrogen) 64-bit
Flash Version: 23.0.0.185

terminal output (as normal user):
$ google-chrome
--2016-12-10 20:54:08--  https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 216.58.208.46, 2a00:1450:4001:815::200e
Connecting to clients2.google.com (clients2.google.com)|216.58.208.46|:443... connected.

Failed to get crash dump id.
Report Id: 
Segmentation fault (core dumped)
$

from systemctl status abrtd -l (as root):
    Dec 10 15:26:10 localhost.localdomain abrt-server[14419]: Package 'google-chrome-stable' isn't signed with proper key
(I downloaded chrome from https://www.google.com/intl/en/chrome/browser/desktop/index.html)

from abrt-cli list (as normal user)
id 0da44a311008c64d5d71a262a7c0fe6a0907147a
Directory:      /var/tmp/abrt/ccpp-2016-12-10-20:38:16-3718
executable:     /opt/google/chrome/chrome
package:        google-chrome-stable-55.0.2883.75-1
time:           Sat 10 Dec 2016 08:38:16 PM EAT
uid:            1000