Add Chromium flag --disable-ipc-flooding-protection

[jennifer-shehane]

Current behavior:

Currently, some of our end-to-end tests for Cypress lock up when run in Chrome (oddly enough, this seemed to only affect MacOS??) They do not lock up in Electron. Where is stalls, this message is printed to the console.

jquery.js:7285 Throttling navigation to prevent the browser from hanging. See https://crbug.com/882238. Command line switch --disable-ipc-flooding-protection can be used to bypass the protection

Desired behavior:

Disable IPC (Inter-process Communication) flooding protection in Cypress. This was also one of the flags mentioned in #3633 that Puppeteer automatically passes through their testing, so adding this would partially address this.

Steps to reproduce: (app code and test code)

In local development of Cypress:

cd packages/server
npm run test ./test/performance/cy_visit_performance_spec.js

Essentially what this test does is cy.visit() a url 100 times really really fast.

Additional information

From Chromiums code, trying to figure out what this flag actually does.

"Some javascript code can flood the inter process communication system. "
"This protection limits the rate (calls/seconds) at which theses function "
"can be used. This flag disables the protection. This flag is deprecated "
"and will be removed in Chrome 76. Use the switch "
"--disable-ipc-flooding-protection instead.";

// Disables the IPC flooding protection.
// It is activated by default. Some javascript functions can be used to flood
// the browser process with IPC. This protection limits the rate at which they
// can be used.

[cypress-bot]

The code for this is done in cypress-io/cypress#5310, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 3.5.0.