New issue
Advanced search Search tips
Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2015



Sign in to add a comment
link

Issue 672: Wait 60 seconds for chrome to start up on all OS and 30 seconds for chrome shutdown on Mac and Linux.

Reported by st...@chromium.org, Jan 15 2014 Project Member

Issue description

This is to improve reliability in resource starving situations.
 

Comment 1 by st...@chromium.org, Jan 15 2014

Project Member
Labels: Pri-0

Comment 2 by st...@chromium.org, Jan 18 2014

Project Member
Some users ran into error "unable to discover open pages". This is because chromedriver failed to find a opened tab in the browser within 20 seconds after it started chrome.

Some other users also ran into error "cannot kill Chrome". This is because chrome didn't exit within 5 seconds after chromedriver tried to kill the chrome process.

Comment 3 by st...@chromium.org, Jan 19 2014

Project Member
Status: ToBeReleased

Comment 4 by st...@chromium.org, Feb 3 2014

Project Member
Status: Closed
Released in 2.9

Comment 5 by st...@chromium.org, Feb 3 2014

Project Member
 Issue 679  has been merged into this issue.

Comment 6 by st...@chromium.org, Feb 7 2014

Project Member
 Issue 679  has been merged into this issue.

Comment 7 by bino...@gmail.com, Feb 10 2014

Curious, does this mean always wait 60s regardless, all the time?

Comment 8 by st...@chromium.org, Feb 10 2014

Project Member
Nope, 60s is the maximum.

Comment 9 by samu...@chromium.org, Feb 21 2015

Status: Fixed

Sign in to add a comment