-
-
Notifications
You must be signed in to change notification settings - Fork 737
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
Jest leaking memory even after calling nock.restore() #2383
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please avoid duplicates
Reproducible test case
https://github.com/RedTn/nock-memory-leak
Nock Version
13.2.8
Node Version
16.10.0
TypeScript Version
No response
What happened?
Was asked to create a new issue: #2077 (comment)
The README says to call nock.restore() to prevent a memory leak in jest.
https://github.com/nock/nock#memory-issues-with-jest
However, in my sample repo this is not the case.
This is similar but not the same as #2358, simply importing
nock
is enough to cause a memory leakWould you be interested in contributing a fix?
The text was updated successfully, but these errors were encountered: