Cypress: Cypress test runner / dev tools are blanked out

[jean-smaug]

Current behavior:

Desired behavior:

See the cypress app ^^

Steps to reproduce:

Just run a test

Versions

On Cypress 2.1.0, MacOS High Sierra with Chrome Canary 68.0.3400.0.
Maybe it's on canary's side but if the next version of Chrome introduce some breaking changes, it's something to be aware of

[jennifer-shehane]

I'm not experiencing this in Canary 68.0.3400.0.

It looks like you have some other extensions installed in your Canary browser. Could you disable all of those first to further isolate the issue to Cypress? Let me know if the issue still occurs after that. Thanks.

[lobor]

I have same issue

Chrome 67.0.3396.79 on Mac

[jennifer-shehane]

We'll need a reproducible example that we can run to get this to happen for us. I do not think this issue is likely relevant to the specific Chrome version, but some other reason that we'd love to track down. Thanks!

[jennifer-shehane]

@lobor Also, as stated above, if you could you disable all of those first to further isolate the issue to Cypress? Let me know if the issue still occurs after that. Thanks.

[simsim2006]

so i had the same issue. I just remember i deleted my project's node_module/ folder a few minutes before facing that issue, and then i did a yarn install/npm install. I don't know if it can help you to reproduce the issue.

In my case, i use Electron instead of Chrome as a workaround of this issue

[jennifer-shehane]

Yeah, deleting the node_module folder did not affect the runner. Did you happen to touch the App Data folder? Like File > App Data in menu bar?

I'm pretty confused on this one. :(

[simsim2006]

No i never touched that folder no. Can i try to empty it without any risk ?

[jennifer-shehane]

Yes, I suppose it is worth a try:

• Goto File -> View App Data
• Delete everything in here
• Close cypress and open it up again

[simsim2006]

just tested but doesn't help

[simsim2006]

and when i open a new tab on the browser window opened by cypress, it show the same... so seems like an issue with the "piloted browser" (i don't know how to call that)

[Antontelesh]

I have the same issue.

I tried to remove cypress cache folder and reinstall it again.
But that did not help.

[brian-mann]

You all might want to pass in arguments to chrome to start disabling things like the GPU

--disable-gpu

You can do that in your pluginsFile as documented here: https://docs.cypress.io/api/plugins/browser-launch-api.html

For a full list of command line arguments use this:

https://peter.sh/experiments/chromium-command-line-switches/

Alternatively you could also remove the ones we pass in by default to see if those trigger it. Either something we're adding or something you need to add will fix this. But without a reproducible machine we won't be able to figure it out on our own.

You might want to start adding a bunch of the --disable-* flags

[ankri]

I am on

• Mac Sierra 10.12.6
• Cypress 3.0.1
• Chrome 67.0.3396.87

--disable-gpu did the trick for me, thanks!

[ValentinH]

I can confirm that adding --disable-gpu fixes the issue.

I've also tried to remove all the default flags and it didn't fix it.

Then I have tried adding each --disable-gpu-*** and 2 of them also fixed the issue (separately):

• --disable-gpu-compositing (Prevent the compositor from using its GPU implementation.)
• --disable-gpu-rasterization (Disable GPU rasterization, i.e. rasterize on the CPU only.)

[dcastil]

I have the same issue after updating to Chrome v67. The window looks like this:

Mac OS High Sierra v10.13.5
Cypress v3.0.2
Google Chrome v67.0.3396.99

I can also confirm that adding one of

--disable-gpu
--disable-gpu-compositing
--disable-gpu-rasterization

solves the problem for me.

[jennifer-shehane]

Closing since there is a suggested workaround available.