-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Memory increasing in empty project #9524
Comments
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🐛 Bug Report
There are technically 2 issues (but this report will focus on the memory issue)
To Reproduce
Steps to reproduce the behavior:
Create a loop of many tests and run them. I tested using 1000 tests in 100 files (100k tests), but the same can be done in a single file. Most obvious when using the
--runInBand
flag along with--logHeapUsage
Expected behavior
Memory usage should at the very least drop after each file instead of continuing to grow.
Link to repl or repo (highly encouraged)
v25
Repository
Tests
v24
Repository
Tests
v23
Repository
Tests
To test the above, clone the repo and run
yarn test:debug
envinfo
Despite the above OS/CPU specs, the same can be seen from the linked test results from GitHub Actions.
The text was updated successfully, but these errors were encountered: