-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Look into adding --disable-dev-shm-usage
Chrome flag
#5336
Comments
Did anyone else notice that this command is not working for the new chrome (80)? I upgraded my chrome and the chrome crashes, just like in earlier versions, before this code. |
Updated the workaround in the OP for Cypress 4.0.0+. @Jacek-fstack so Chrome 80 successfully launches with |
I was getting this error constantly during normal usage. Usually from doing things like alt-tabbing. I was using the electron version, not chrome, to launch Cypress.
However, I was running Cypress itself inside of a Docker container. I ended up solving this by mounting the shm directory |
On macOS there is no |
Note that in the workaround from @flotwig above, the |
@adamalton Thanks! I've updated the original comment to reflect this. |
The code for this is done in cypress-io/cypress#9242, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior:
Cypress doesn't pass
--disable-dev-shm-usage
: https://github.com/cypress-io/cypress/blob/develop/packages/server/lib/browsers/chrome.coffee#L21But Puppeteer does: https://github.com/GoogleChrome/puppeteer/blob/master/lib/Launcher.js#L37
However, in this commit that adds
--disable-dev-shm-usage
, it seems to cause failures to start Chrome: 7247dcfIt may be because Cypress does not run Chrome headlessly: #832
Desired behavior:
Cypress passes
--disable-dev-shm-usage
so that machines with small/dev/shm
s can run Cypress.Original issue: #3633
Workaround (4.0.0 and up)
A user can modify Chrome flags by adding this in their pluginsfile:
Workaround (pre-4.0.0)
A user can modify Chrome flags by adding this in their pluginsfile:
Edited by @jennifer-shehane to note
browser.family
to equalchromium
The text was updated successfully, but these errors were encountered: