Skip to content
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

firefoxGcInterval: null does not work as documented #6825

Closed
jennifer-shehane opened this issue Mar 24, 2020 · 2 comments · Fixed by #6826 or Flygsand/site#83
Closed

firefoxGcInterval: null does not work as documented #6825

jennifer-shehane opened this issue Mar 24, 2020 · 2 comments · Fixed by #6826 or Flygsand/site#83
Labels

Comments

@jennifer-shehane
Copy link
Member

jennifer-shehane commented Mar 24, 2020

Current behavior:

It says in our docs, to turn off firefoxGcInterval for both runMode and openMode, I can just set the following: https://on.cypress.io/configuration#firefoxGcInterval

{
  "firefoxGcInterval": null
}

But this throws an error

Screen Shot 2020-03-24 at 3 37 31 PM

I don't see any indication of this setting ever having worked (tried back to 4.0.2).

Full stack trace:

TypeError: intervals is null
    createIntervalGetter/<@https://docs.cypress.io/__cypress/runner/cypress_runner.js:157219:22
    install/<@https://docs.cypress.io/__cypress/runner/cypress_runner.js:157242:30
    listener@https://docs.cypress.io/__cypress/runner/cypress_runner.js:150130:19
From previous event:
    extend/events.emitThen@https://docs.cypress.io/__cypress/runner/cypress_runner.js:150132:22
    extend/events.proxyTo/</parent[fn]@https://docs.cypress.io/__cypress/runner/cypress_runner.js:150082:29
    action@https://docs.cypress.io/__cypress/runner/cypress_runner.js:145451:32
    fire@https://docs.cypress.io/__cypress/runner/cypress_runner.js:151440:18
    testBeforeRunAsync/<@https://docs.cypress.io/__cypress/runner/cypress_runner.js:151450:14
From previous event:
    testBeforeRunAsync@https://docs.cypress.io/__cypress/runner/cypress_runner.js:151448:18
    onRunnableRun@https://docs.cypress.io/__cypress/runner/cypress_runner.js:152462:14
    action@https://docs.cypress.io/__cypress/runner/cypress_runner.js:145442:61
    patchRunnableRun/Runnable.prototype.run@https://docs.cypress.io/__cypress/runner/cypress_runner.js:151262:13
    ../driver/node_modules/mocha/lib/runner.js/</Runner.prototype.runTest@https://docs.cypress.io/__cypress/runner/cypress_runner.js:92961:10
    next/<@https://docs.cypress.io/__cypress/runner/cypress_runner.js:93087:12
    next@https://docs.cypress.io/__cypress/runner/cypress_runner.js:92870:14
    next/<@https://docs.cypress.io/__cypress/runner/cypress_runner.js:92880:11
    next@https://docs.cypress.io/__cypress/runner/cypress_runner.js:92782:14
    ../driver/node_modules/mocha/lib/runner.js/</Runner.prototype.hook/<@https://docs.cypress.io/__cypress/runner/cypress_runner.js:92848:9
    timeslice@https://docs.cypress.io/__cypress/runner/cypress_runner.js:86774:27

Looks like a null value is not being handled at all here:

https://github.com/cypress-io/cypress/blob/develop/packages/driver/src/util/firefox_forced_gc.ts#L3:L3

Desired behavior:

Well, the question is - is this a bug in the code or was this just documented wrong. Not sure which requires updating.

Test code to reproduce

cypress.json - open via cypress open or cypress run in Firefox 72.0.2

{
  "firefoxGcInterval": null
}

Versions

4.0.0+

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Mar 24, 2020

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

@cypress-bot cypress-bot bot added stage: pending release and removed stage: needs review The PR code is done & tested, needs review labels Mar 24, 2020
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Mar 30, 2020

Released in 4.3.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v4.3.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
1 participant