Tests are failing in Google Chrome 52 WebDriverException:unknown error: unable to discover open Page

[Robins Mathew]

My google chrome was updated to 52 yesterday and all the test started failing with org.openqa.selenium.WebDriverException: unknown error: unable to discover open pages error

Chrome Driver used - 2.21 and 2.22

Selenium Version - 2.53

Error displayed - 

org.openqa.selenium.WebDriverException: unknown error: unable to discover open pages (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 60.69 seconds Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15 17:00:58'

Reverted back to Google Chrome version 51 and everything is fine.

Have anyone faced this today?

[Praveen iG]

Hello,

I had read from this forum earlier that adding the following solved the issue. Give it a try.

chromeOptions.AddArguments("no-sandbox");

Thanks,
Praveen

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/09ff550b-80d2-4835-870e-e83cc9232edb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robins Mathew]

Hi Praveen,

Thanks for the reply. 

I have seen this solution but it looks like its a workaround. If selenium is not running in the new version of chrome then it should be resolved in the next version of selenium or chromedriver rather than doing the workarounds to resolve the issue temporarily.

Anyways I have my tests running without any issues when I use chrome version 52.

Here is the no-sandbox option, Reading this I dont feel like I should use this to get it work. What do you think?

allow-no-sandbox-job

Enables the sandboxed processes to run without a job object assigned to them. This flag is required to allow Chrome to run in RemoteApps or Citrix. This flag can reduce the security of the sandboxed processes and allow them to do certain API calls like shut down Windows or access the clipboard. Also we lose the chance to kill some processes until the outer job that owns them finishes. ↪

Thanks,

Robins

[Praveen iG]

Hi Robins,

I agree that this is a workaround. Since your tests run fine on v51 of chrome, I suggest using that. You can find more information on sandbox from this answer on stack exchange.

Regards,

Praveen

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/d757f9bd-b11e-40f6-ad1c-bbdbbf6d7811%40googlegroups.com.

[Rocco Balsamo]

Hey folks,

I solved this problem by updating to chromedriver 2.24 available here: https://sites.google.com/a/chromium.org/chromedriver/downloads.

For good measure, I also updated my selenium jar to 3.0.0, available here: http://www.seleniumhq.org/download/. I'm not sure if this step is required.

Good luck!