-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After update to cypress:including_4 + we have just a blank window for Chrome browser #270
Comments
Can you open the DevTools? Are there any errors printed there when the browser opens? We have tests with the latest Chrome browser - this is running in I would recommend removing options from the docker config to see which ones are affecting the run. cc @bahmutov any thoughts? |
I have a similar issue. I'm running If I select Electron (v78) from the browser dropdown, and run my tests that way, then the browser appears and works as expected. Aside: |
Also having this issue with only 4.0.2. Extremely minimal setup, using the spec.js from https://github.com/bahmutov/demo-docker-cypress-included In fact if you change the version in |
I believe this is related (and may be the issue itself): https://bugs.chromium.org/p/chromium/issues/detail?id=1026950 |
I managed to fix it. You need to set three environment variables, either when running via docker, or within the docker image build:
or
Explanation The bug only happens when you are using a remote X11 interface, for example I spent all day today exploring browser automation frameworks. I found this bug in Cypress and then went to look at playwright, where I found the same bug. This solution fixes both. The docker example + docker images should probably be updated |
@milesrichardson Thanks for the detailed response and debugging. We will move this into our docker-images repo since this is more related to environment setup than the Cypress product itself. |
I tried https://github.com/bahmutov/cypress-open-from-docker-compose with Cypress 4.0.2 and Chrome browser with local X11 forwarding and saw the problem. Setting the env variables to disable shared memory fixed the problem. Will add these variables and notes to the new Docker containers. |
As I understand the problem fixed in the new https://github.com/cypress-io/cypress-docker-images/tree/master/included/4.1.0 container. Amazing, great job! Thanks. |
Current behavior:
Using Docker image cypress:including_3.8.0 - everything works fine.
We use this mapping to make
cypress open
workThe host OS is Ubuntu 18.04, latest updates.
But after update to cypress:including_4 + we have just a blank screen for Chrome browser.
Test runner starts without problems, but running any test does not open Chrome, just a blank window appears.
Nevertheless, I can see that the test is running in the console log. We just cannot see it in Chrome.
This is the starting log. I tried with
export DEBUG=cypress:*
option and cannot see any errors except these.Desired behavior:
Chrome browser opens normally with Cypress interface and runs the test as it works with Docker image cypress/included:3.8.0
Test code to reproduce
Use
cypress/uncluded:4.0.2
, have such docker configRun the command such as
It works with 3.8.0
It doesn't for 4.0.2
I think that issue is the newer chrome browser. Something changed starting from Chrome 78.
These are options which worked for us with Chrome 77
Now it doesn't work with or without these options.
With Cypress builds with Chrome 78-80 we cannot connect to Chrome anymore?
What options could be missing?
Versions
Ubuntu 18.04, Chrome 80, Cypress 4.0.2
The text was updated successfully, but these errors were encountered: