New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 819998 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Mar 2018
Cc:
█ sandeepkumars@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

chrome can only working on no sandbox mode on centos 7

Reported by isaac4...@gmail.com, Mar 8 2018 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3355.0 Safari/537.36

Steps to reproduce the problem:
1. OPEN TERMINAL
2. START GOOGLE-CHROME
3. BOOM

What is the expected behavior?
open noraml

What went wrong?
--2018-03-08 18:43:34--  https://clients2.google.com/cr/report
Connecting to 127.0.0.1:56597... connected.
Proxy request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/4’

Crashed report ID: 643160ab6c2fabe3

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? No 

Chrome version: 66.0.3355.0  Channel: dev
OS Version: 
Flash Version:

Comment 1 by sandeepkumars@chromium.org, Mar 9 2018

Cc: sandeepkumars@chromium.org
Components: Internals>Network
Labels: Needs-Triage-M66
Mergedinto: 791430
Status: Duplicate (was: Unconfirmed)
Magic signature and stack trace of the above Crash I'd looks similar to issue 791430. Hence duping into it.

Thanks!!

Comment 2 by isaac4...@gmail.com, Mar 14 2018 

It seems like I can not open Issue 791430
►

Sign in to add a comment