Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Crash after allocation failure #1077

Closed
jhartma opened this issue Dec 16, 2017 · 1 comment
Closed

Crash after allocation failure #1077

jhartma opened this issue Dec 16, 2017 · 1 comment
Assignees
Labels
type: duplicate This issue or pull request already exists

Comments

@jhartma
Copy link

jhartma commented Dec 16, 2017

  • Operating System: Arch Linux
  • Cypress Version: 1.2.0, but also all previous versions
  • Browser Version: shipped Electron version

Is this a Feature or Bug?

Bug

Current behavior:

I have a quite extensive test suite running. On their own, the tests run just fine, but when I click on the "Run all tests" button in the electron window, Cypress crashes after a while. When running tests in the console, it works fine.

<--- Last few GCs --->

  272175 ms: Mark-sweep 1398.6 (1504.2) -> 1397.9 (1504.2) MB, 408.7 / 3.3 ms [allocation failure] [GC in old space requested].
  272755 ms: Mark-sweep 1397.9 (1504.2) -> 1397.9 (1489.2) MB, 579.9 / 35.7 ms [last resort gc].
  273252 ms: Mark-sweep 1397.9 (1489.2) -> 1397.5 (1489.2) MB, 496.1 / 33.5 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x149c585deba9 <a Window with map 0x8a3a160c709>
    1: StringReplaceGlobalRegExpWithFunction [native regexp.js:~448] [pc=0x154714707ecb](this=0x2ee831a2a489 <JS Global Object>,W=0x2bc4b839e749 <Very long string[1425151]>,C=0xeb37ade4db9 <JS RegExp>,aw=0x9e572c5521 <JS Function (SharedFunctionInfo 0x3e75501b2559)>)
    2: RegExpReplace [native regexp.js:~528] [pc=0x1547146cb455](this=0xeb37ade4db9 <JS RegExp>,D=0x2bc4b83...

Desired behavior:

Should continue running tests

@brian-mann
Copy link
Member

Closing this as a duplicate. This is a well known and documented aspect of Cypress. The GUI is not built to run all tests because of the way Cypress creates debuggability.

The CLI is the only place where you should be running all your tests and it opts for performance and longer runs as opposed to the GUI. The GUI is only there for test writing and iterations, whereas the CLI is there for running your tests to completion.

If you want all the details check out this issue - we have major changes coming to this (hopefully in Dec) which solve / address these issues.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
type: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants