We've recently experienced some peculiar errors when processing capybara-based automation scripts on Heroku. Most of the time, the error returned did not show anything useful…
yet for a brief period of time, following error was reported when attempting to access capybara session
Session Deleted Because Of Page Crash Selenium Webdriver
- Org.openqa.selenium.WebDriverException: unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed (Session info: chrome=66.0.3359.181) (Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Linux 4.4.0-72-generic x8664).
- 在docker上跑Selenium+ChromeDriver+Chrome无头模式报错: UnknownError: unknown error: session deleted because of page crash from tab crashed.
- OpenQA.Selenium.WebDriverException: unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed (Session info: chrome=77.0.3865.90) at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse) at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters) at OpenQA.Selenium.Remote.RemoteWebDriver.
- Selenium::WebDriver::Error::UnknownError: unknown error: session deleted because of page crash from tab crashed Finally, after spotting this comment we've reduced chrome window size from 1920,1200 to 1440,900 and the problem is no longer present.
It will throw an exception from Selenium, because ChromeDriver won't be able to process the post-command cleanup once the page crashes. But check the exception, because Chrome can refuse the.
Selenium Chrome Session Deleted Because Of Page Crash
Session Deleted Because Of Page Crash Selenium Webdriver
- Org.openqa.selenium.WebDriverException: unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed (Session info: chrome=66.0.3359.181) (Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Linux 4.4.0-72-generic x8664).
- 在docker上跑Selenium+ChromeDriver+Chrome无头模式报错: UnknownError: unknown error: session deleted because of page crash from tab crashed.
- OpenQA.Selenium.WebDriverException: unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed (Session info: chrome=77.0.3865.90) at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse) at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters) at OpenQA.Selenium.Remote.RemoteWebDriver.
- Selenium::WebDriver::Error::UnknownError: unknown error: session deleted because of page crash from tab crashed Finally, after spotting this comment we've reduced chrome window size from 1920,1200 to 1440,900 and the problem is no longer present.
It will throw an exception from Selenium, because ChromeDriver won't be able to process the post-command cleanup once the page crashes. But check the exception, because Chrome can refuse the.
Selenium Chrome Session Deleted Because Of Page Crash
Finally, after spotting this comment we've reduced chrome window size from 1920,1200
to 1440,900
and the problem is no longer present.
Session Deleted Because Of Page Crash Selenium Sulfide
The root reason is unknown, but most likely it is at least partially related to running out of memory (reference). Most of recommendations when using docker in this scenario, was to increase shm-size
, by providing --shm-size=2g
to docker run
. That was not an option for us though…
Hope it helps in case you run into similar situation.