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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory increasing in empty project #9524

Closed
alexbarnsley opened this issue Feb 5, 2020 · 3 comments
Closed

Memory increasing in empty project #9524

alexbarnsley opened this issue Feb 5, 2020 · 3 comments

Comments

@alexbarnsley
Copy link

馃悰 Bug Report

There are technically 2 issues (but this report will focus on the memory issue)

  1. Memory increases with every test that is performed.
  2. There was a regression between v23 and v24 which resulted in slower tests

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

System:
    OS: macOS 10.15.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 12.14.1 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.11.2 - ~/.npm-packages/bin/npm
  npmPackages:
    jest: Omitted due to testing v23-25

Despite the above OS/CPU specs, the same can be seen from the linked test results from GitHub Actions.

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Feb 17, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2023
@github-actions
Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants