Chrome 93

[Marc Webster]

Hello all

The latest live version of Chrome is 93.0.4577.63, but ChromeDriver is at 93.0.4577.15 - are there any plans to release a new version? 

This combo seems to work pretty well when run manually from the command line, but running under task scheduler, it has all sorts of issues, and mostly just hangs when trying to start the browser. About one in five times, it will work.

I'm still digging on this (previously thought it was to do with permissions, temp directories, localhost confusion, etc), but if it's just as simple as needing a new release, I'll hold off.

Thanks,

Marc

[Aysun Yilmaz]

is there any open tickets regarding this issue? i am using teamcity and we have the similar issues.

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/b580942b-5f63-4ae4-91e7-8b92f8bacf08n%40googlegroups.com.

[Paul Brandhagen]

Same issue for our team... works fine from command prompt, but Windows Task Scheduler can't seem to create a chrome session.

Hoping a new chromedriver (not the one from the end of July) fixes this...

-Paul B

[Paul Brandhagen]

I just tried using the --disable gpu option in my chromedriver options... and it totally resolved all problems with Windows Task Scheduler
These posts helped me decide to try it

https://stackoverflow.com/questions/48450594/selenium-timed-out-receiving-message-from-renderer/52340526#52340526

https://stackoverflow.com/questions/69034343/chromedriver-session-timeouts-in-version-93

-Paul B

[pgcl...@gmail.com]

Raised similar issue in another thread - https://groups.google.com/g/chromedriver-users/c/COktL3U3zYk 

We run our tests under a windows service account.

Will try the --disable gpu and update

Ideally this would not be required.

[Vivek Verma]

Similar issue we faced , while executing test from jenkins..., with disable gpu , we are able to resolve it.

[Marc Webster]

Thanks Paul, I'd scoured StackOverflow before posting, but somehow didn't see that one. That sorts it, thanks - we may make this the default setup for future.

[pgcl...@gmail.com]

Update

--disable gpu resolved the issue for us

[pgcl...@gmail.com]

update flag name is: 

--disable-gpu