Session Deleted Because Of Page Crash Selenium

Posted on by

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 Chrome

Selenium.common.exceptions.WebDriverException' unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed. となってしまいます。 chrome.logを見たところ、キャプチャを撮るところでエラーになっているようでした。.

Session Deleted Because Of Page Crash Selenium

Finally, after spotting this comment we’ve reduced chrome window size from 1920,1200 to 1440,900 and the problem is no longer present.

Selenium

Session Deleted Because Of Page Crash Selenium Webdriver

  • When the Selenium test is run in a Windows Server docker container, the test fails with 'session deleted because of page crash'. When the Selenium test is run in a custom build.NET Framework oriented container in docker, the test executes successfully. You cannot run a Selenium test in a stock Windows Server container at this point.
  • 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.
  • 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.
Session deleted because of page crash selenium webdriverSelenium

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.