Geek Answers Handbook

Chromdriver2.21.2 crash "no such session"

I am trying to do an automatic test for my webpage and I am using Jasmine in tandem with selenium.

When testing on chrome (using a chrome rib) I get an unpredictable error below. This happens often enough when I run a test suite that almost never ends.

I found evidence of this error, but cannot find a reliable answer: https://bugs.chromium.org/p/chromedriver/issues/detail?id=732 (if it was for chrome, and I use chrome)

WebDriverError: no such session (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Mac OS X 10.11.5 x86_64) at WebDriverError (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/error.js:27:10) at Object.checkLegacyResponse (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/error.js:639:15) at parseHttpResponse (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/http/index.js:538:13) at /Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/http/index.js:472:11 at ManagedPromise.invokeCallback_ (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:1379:14) at TaskQueue.execute_ (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:2913:14) at TaskQueue.executeNext_ (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:2896:21) at /Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:2820:25 at /Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:639:7 at process._tickCallback (node.js:369:9) From: Task: WebElement.isDisplayed() at Driver.schedule (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/webdriver.js:377:17) at WebElement.schedule_ (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/webdriver.js:1744:25) at WebElement.isDisplayed (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/webdriver.js:2110:17) at driver.findElements.then.error (/Users/XXXXXXX/Documents/sweetmeeting/Test/front_end_testing/spec/dashboard_tester.js:251:34) at ManagedPromise.invokeCallback_ (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:1379:14) at TaskQueue.execute_ (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:2913:14) at TaskQueue.executeNext_ (/Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:2896:21) at /Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:2775:27 at /Users/XXXXXXX/Documents/sweetmeeting/node_modules/selenium-webdriver/lib/promise.js:639:7 at process._tickCallback (node.js:369:9)
+5
source share
2 answers

We also struggled with this problem for a long time and recently resolved it, so I thought I would post it here if it helps someone else.

It turns out that for us it is connected with memory. We run our tests inside the docker container, and the size of the de / shm decoder is 64 MB by default. Increasing this resolved the “no such session” problem for us.

We use docker compose, so just add shm_size: 256M to the docker-compose.yml file.

+8
source

I recently came across this exception. It also turned out to be non-deterministic at first, but after a thorough investigation, I realized that this happens deterministically if you call ChromeDriver.Close () and then try to find FindElement.

In my case, ChromeDriver.Close () was called in the exception handler of the previous test, which occurred due to a synchronization problem. This only affected the next test, so he added to the feeling that this problem is uneven. But, as I said, my investigation showed that it is deterministic.

Having said that, this is my experience with this error. Maybe your case is different ...

+6
source

More articles:


All Articles