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

[Bug]: Linearly-increased memory usage when using multiple jest.config.ts files + projects #12159

Closed
grxy opened this issue Dec 17, 2021 · 1 comment · Fixed by #12160
Closed

Comments

@grxy
Copy link
Contributor

grxy commented Dec 17, 2021

Version

27.4.5

Steps to reproduce

  1. Clone https://github.com/grxy/jest-memory-issue
  2. Install dependencies with yarn
  3. Run yarn jest-js and make note of the reported heap size
  4. Run yarn jest-ts and notice that the heap size has increased
    It appears to increase linearly based on the number of jest.config.ts files being used.

Expected behavior

Memory usage should be consistent when using multiple jest.config.ts files + the projects config option.

Actual behavior

Memory usage increases when using multiple jest.config.ts files + the projects config option. Tests also execute more slowly.

Additional context

No response

Environment

System:
    OS: macOS 11.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.18.1/bin/yarn
    npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm
  npmPackages:
    jest: ^27.4.5 => 27.4.5
@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 Jan 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant