New issue
Advanced search Search tips

Issue 820499 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-03-26
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

browser won't start - window opens, but is not visible and have to force quit

Reported by mrhega...@gmail.com, Mar 9 2018

Issue description

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

Steps to reproduce the problem:
1. run 'google-chrome-stable' from cmd line

What is the expected behavior?
Chrome will start without issue.  This was fine before update to 65.0.3325.146 

What went wrong?
The only info printed to terminal is:

Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any effect anymore. please remove it from your fonts.conf
[8640:8640:0309/181532.793981:ERROR:sandbox_linux.cc(375)] InitializeSandbox() called with multiple threads in process gpu-process.

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes dk

Chrome version: 65.0.3325.146   Channel: stable
OS Version: 3.13.0-142-generic
Flash Version: 

- Have tried latest Chromium and also same problem
- I completely uninstalled / re-installed - same problem

- 'Local State' file is a giant blob of json and there is no client_id line, but client_id is

"client_id2":"a3377f40-6bfe-4add-bce3-2b0af50fc7ec"
 
Labels: Needs-Triage-M65

Comment 2 by mrhega...@gmail.com, Mar 10 2018

The version 64.0.3282.186 works fine

Comment 3 by mrhega...@gmail.com, Mar 10 2018

The behaviour during the crash is that Chrome appears to start - a new window appears in the task panel.  If you maximise the window it appears to maximise, but doesn't display anything - only the background of the window that was there already.

Chrome never starts after this.  I have to right click on the panel icon and select 'close'.  Then after a few seconds, I get the 'Chrome is not responding' message, and I have to force quit.

This issue occurs 100% of the time for this version.
Unable to reproduce the issue on Debian Rodate using chrome reported version-65.0.3325.146 (stable) as per the steps mentioned in C#0.

Chrome started without any issue from command line (terminal).

Please provide us the OS (Ubuntu/Debian/Mint) where the issue observed with new chrome version(stable/beta...)

If possible provide us the server is from chrome://crashes to proceed further.
Thanks..!
Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback

Comment 6 by mrhega...@gmail.com, Mar 12 2018

DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17
DISTRIB_CODENAME=qiana
DISTRIB_DESCRIPTION="Linux Mint 17 Qiana"
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

Project Member

Comment 7 by sheriffbot@chromium.org, Mar 12 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by mrhega...@gmail.com, Mar 12 2018

> If possible provide us the server is from chrome://crashes to proceed further.

Please can you clarify what is required?  I can't access  chrome://crashes because browser fails to start.

Comment 9 by mrhega...@gmail.com, Mar 12 2018

$ uname -a
Linux sirius 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:13:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Cc: pbomm...@chromium.org kkaluri@chromium.org
Components: UI
Labels: TE-NeedsTriageFromMTV
Since Linux Mint OS is not available with TE team, hence adding "TE-NeedsTriageFromMTV"  label for further triage
Cc: thomasanderson@chromium.org
Labels: -TE-NeedsTriageFromMTV
MTV doesn't have a Mint device as well.   kkaluri@ please check on the available devices and update the bug.
OP: Does chrome start when running with --disable-gpu ?
Yes: --disable-gpu solves the issue :-)

$ google-chrome-stable --disable-gpu
Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any effect anymore. please remove it from your fonts.conf
[6508:6508:0313/174429.500226:ERROR:gpu_process_transport_factory.cc(1019)] Lost UI shared context.
[6508:6546:0313/174430.904413:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[6508:6546:0313/174431.136270:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[6508:6546:0313/174434.726608:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)


GPU info:

$ dmesg | grep fglrx | grep module
[    3.995403] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[    4.003990] fglrx: module verification failed: signature and/or  required key missing - tainting kernel
[    4.018534] <6>[fglrx] module loaded - fglrx 14.30.4 [Sep 15 2014] with 1 minors

thanks for the update

Cc: piman@chromium.org
Please attach the crash IDs now from chrome://crashes
Hi
The crash ids are not showing at the above URL. Perhaps the process never gets to the point of recording the crash.

Comment 16 by piman@chromium.org, Mar 19 2018

Components: -UI Internals>GPU>VendorSpecific
Labels: Needs-Feedback
NextAction: 2018-03-26
It's not clear that a crash causes this. It sounds like a driver-related issue where rendering doesn't work for some reason.

Following the instructions at https://www.chromium.org/developers/bisect-builds-py would be useful to pinpoint the issue, if this is a regression.
The NextAction date has arrived: 2018-03-26

Sign in to add a comment