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

Issue 652782 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome browser not opening intermittently

Reported by minju182...@gmail.com, Oct 4 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Click on the Chrome icon in the taskbar
2. 
3. 

What is the expected behavior?
Chrome Browser should open in a single click

What went wrong?
Chrome.exe process gets started in the task manager, but the browser is not opening. Have to try atleast 2-3 times clicking on the Chrome icon to open up the browser.

Did this work before? Yes Till Chrome version 48, everything was fine.

Chrome version: 53.0.2785.143  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

From Chrome browser version 50 onwards, the issue started happening and while running selenium automated tests in Chrome browser, the browser is not opening intermittently, because of which the tests will fail.
This is preventing us from running our regression tests in latest Chrome [53]. Can you please take a look.

This is not just affecting automation tests. The issue can be reproduced manually too.
 
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
Unable to reproduce this issue on Windows 10 with latest chrome stable version 53.0.2785.143.
Could you please try to create a new profile with no apps and extensions and test the scenario again and let us know the observations.
i am on windows 7 and i can reproduce this manually (intermittently ). I uninstalled and reinstalled latest Chrome stable version and it doesn't have any apps or extensions.This issue is intermittent. Need several tries to reproduce this.

The main problem is this affects our automation test runs, since the browser wont open up, our some tests will fail.

Cc: pbomm...@chromium.org
Labels: -Needs-Feedback M-55 Needs-Bisect
Cc: ranjitkan@chromium.org
Labels: -Needs-Bisect Needs-Feedback
Just tried again on Windows 7 for chrome version 53.0.2785.143 and on Market stable 54.0.2840.59. Tried multiple times by clicking the desktop Icon, Start menu Icon and task bar Icon. Every time chrome launched. Tried on both 32 and 64 Bit chrome versions in both user level and system level of chrome installation.

@ minju182004: Request you to please check your chrome driver once again, if selenium is not invoking chrome. 

Removing Bisect label, please add if required again.

Thanks.!

Comment 5 by bru...@gmail.com, Oct 14 2016

On W10 Enterprise 1511 Chrome will not load beyond the first process created.
It then sits forever in task manager, showing minimal memory usage, and 0 CPU.
Investigation by Procexp shows a suspended subprocess.

Re-install failed to rectify.

This happened after going to 54.0 from 53 which worked fine.
Can confirm on Windows 10 Education.
You need to restart many times to get it work.
Once it is not. I've tried adding "--enable-logging --v=1"
to the command line but there's no debug log appearing in my user dir. 
I tried  --enable-logging --v=1 --user-data-dir=r:\tt
to specify an empty folder as user dir. But chrome didn't put anything inside it.
I think this is similar to  issue#655788 , which should be fixed now on latest Stable i.e., 	54.0.2840.87. 
Unable to reproduce this issue on Windows 10 with latest chrome stable version 53.0.2785.143.

minju182004@, Could you please update your chrome browser to the latest version 54.0.2840.87 and let us know your observations.

minju@- Any latest update available for this issue? Could you please respond for the comment #8 as well.
Can someone who are still able to reproduce the issue please provide a screen cast if possible given we aren't able to reproduce the issue.
Project Member

Comment 11 by sheriffbot@chromium.org, Nov 20 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment