New issue
Advanced search Search tips

Issue 1097 link

Starred by 26 users

Issue metadata

Status: Fixed
Owner: ----
Closed: May 2016



Sign in to add a comment

session deleted because of page crash - Grid v.2.45.0 - Node config : {seleniumProtocol=WebDriver, platform=LINUX, browserName=chrome, maxInstances=5}

Reported by aaleshk...@gmail.com, May 15 2015

Issue description

during tests execution i catched this:
UnknownError: unknown error: session deleted because of page crash
      from tab crashed
        (Session info: chrome=42.0.2311.152)
        (Driver info: chromedriver=2.15.322448 (52179c1b310fec1797c81ea9a20326839860b7d3),platform=Linux 2.6.32-431.11.2.el6.centos.plus.x86_64 x86_64)

 
Project Member

Comment 2 by gmanikpure@chromium.org, May 15 2015

Labels: Needs-Feedback
Could you please provide your testcase ? 

I'm experiencing the same issue on Chrome 43, using Ruby.

Chromedriver 2.15 (Should support v43)
unknown error: session deleted because of page crash
from tab crashed
  (Session info: chrome=43.0.2357.125)
  (Driver info: chromedriver=2.15.322448 (52179c1b310fec1797c81ea9a20326839860b7d3),platform=Linux 3.10-0.bpo.2-amd64 x86_64)

Chromedriver 2.14 (no support for 43 according to documentation)
unknown error: session deleted because of page crash
from tab crashed
  (Session info: chrome=43.0.2357.124)
  (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Linux 3.10-0.bpo.2-amd64 x86_64)

Going to write a simple testcase using as little libraries as possible.
I only experience this within Docker but works ok on "real" machines, is that your case too?

https://github.com/elgalu/docker-selenium/issues/20
Yes, exactly as in https://github.com/elgalu/docker-selenium/issues/20
i have the same issue and the same logs.
And this issue reproduces only with Grid in Docker and not only with https://github.com/elgalu/docker-selenium.
The same i have with https://github.com/SeleniumHQ/docker-selenium
I was able to reproduce it once in a docker container, but even though its in a container its not reproducable anymore.

This is the code I used, as its not reproducable (yet) I'm unable to try the selenium ruby example:

require 'watir-webdriver'
b = Watir::Browser.new :chrome
b.goto 'http://google.com'

element = b.element(:name => 'q')
element.send_keys "Hello WebDriver!"
element.send_keys :enter

puts b.title
b.quit

I haven't been able to solve it, somehow seems related to terminal multiplexer http://stackoverflow.com/questions/25777000/chrome-page-crash-when-running-selenium-and-capybara-under-tmux and maybe docker is doing some magic with that ultimately causing the problem. I discarded that was related to Xvfb or Xdummy video driver by using Xpra and X session FWD to a real display.

This issue is preventing us from testing Chrome in docker seleniums meaning we have to provision some real machines to keep doing the tests.

Haven't found anything yet, but just updated to 2.16 and is still an issue:

unknown error: session deleted because of page crash
from tab crashed
  (Session info: chrome=43.0.2357.125)
  (Driver info: chromedriver=2.16.333243 (0bfa1d3575fc1044244f21ddb82bf870944ef961),platform=Linux 3.10-0.bpo.2-amd64 x86_64)
Any update on this? We are also getting this issue consistently in our docker image. Whether we run the image in privileged mode or not the issue remains
Someone has to provide a reproducible test case.
Hi,

Below is a 100% reproducible test case.

Launch Chrome in docker image

docker run -d -p 4444:4444 selenium/standalone-chrome

run the below python script and it will always raise an exception

from selenium import webdriver
from selenium.webdriver.common.desired_capabilities import DesiredCapabilities
cap = DesiredCapabilities.CHROME
driver = webdriver.Remote(command_executor="http://127.0.0.1:4444/wd/hub/", desired_capabilities=cap)
driver.get("http://www.google.com/")
print driver.page_source
driver.get("http://www.google.com/adwords")
print driver.page_source


Exception:
Message: unknown error: session deleted because of page crash
from tab crashed
  (Session info: chrome=43.0.2357.134)
  (Driver info: chromedriver=2.16.333243 (0bfa1d3575fc1044244f21ddb82bf870944ef961),platform=Linux 3.16.0-38-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 56 milliseconds
Build info: version: '2.46.0', revision: '87c69e2', time: '2015-06-04 16:16:47'

I think it is not related to ChromeDriver as can duplicate by manually open the page from chrome running on docker.

https://code.google.com/p/chromium/issues/detail?id=517113
Yeah looks to be an issue with Google Chrome within Docker (not sure if limited to selenium/node-chrome image). I can also visit http://www.google.com/adwords manually and the tab will crash.
Yes it is not related to chromedriver. Chrome 42 - 44 crashes when manually open ttp://www.google.com/adwords

I am not able to open mentioned above duplicate
https://code.google.com/p/chromium/issues/detail?id=517113

Is there issue already opened for Chrome browser in docker. Should I submit a new one for Chromium? 

We are running into similar issue with our application same as with  
We use own docker configuration similar to selenium/node-chrome-debug

Steps to reproduce manually on public selenium image:
docker run -d -p 4444:4444 --name selenium-hub selenium/hub
docker run -it -p 5900:5900 --link selenium-hub:hub selenium/node-chrome-debug

start vnc viewver on default docker IP 127.0.0.1:5900
or for boot2docker IP at 192.168.69.103:5900
(default password is 'secret')

Right mouse click. Open Applications\Terminal Emulators\XTerm
run following commands
> sudo su - seluser
> google-chrome

In google chrome window type
http://www.google.com/adwords

It loads page and then shows: Aw, Snap!

It is reproducible in all Crome browsers starting 42 (till latest 44)
Currently on Chrome/44.0.2403.155

It is not reproducible on the same selenium image with older Chrome/41.0.2272.89

Please refer correct duplicate or let me know where I can submit this issue? 
I can provide additional details, logs if needed?
Cc: agautam@chromium.org vladimir...@gmail.com tarunlal...@gmail.com
 Issue 772  has been merged into this issue.
Project Member

Comment 17 by gmanikpure@chromium.org, Dec 1 2015

 Issue 772  has been merged into this issue.
Project Member

Comment 18 by gmanikpure@chromium.org, May 5 2016

Cc: -tarunlal...@gmail.com -vladimir...@gmail.com -agautam@chromium.org
Labels: -Needs-Feedback
Status: Fixed (was: Unconfirmed)
Closing the issue since Chrome issue (https://bugs.chromium.org/p/chromium/issues/detail?id=522853) was fixed in v49.

Sign in to add a comment