Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

168
Views
Out of memory issue with Chrome and unit tests

I have a test suite of around 800 tests in a repository. When I run the tests locally I end up with an Aw Snap screen at some point during the tests running. It's more or less running on the build server (running headless), but locally it breaks almost every time.

Is there any way to free up memory to make it possible to run through the tests locally again? It's an issue that recently started to appear and we haven't changed the unit tests to something that should cause this issue so I am afraid that it has to do with a Chrome update or so.

Chrome either loses connection to the dev tools with a Render Process Gone error or DevTools was disconnected from the page.

If I run the tests in incognito it actually says it ran out of memory.

We have an index file that runs WCT.loadSuites([arrayOfSuites]) and each unit test have their own file with suite(), setup and tests.

We're using Polymer 3.

Thanks

about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!