-
-
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
[Bug]: Memory leak when importing multiple @aws-sdk libraries #15390
Comments
This issue is stale because it has been open 30 days 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. |
1 similar comment
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. |
Version
29.7.0
Steps to reproduce
npm install
npm test -- --detectLeaks
Expected behavior
It should not detect any leak
Actual behavior
If you take a heap snapshot at the end of the test you'll see that the garbage collector is not removing the the imported modules at the end of a test suite.
Additional context
A heap snapshot at the end of the tests does indeed show duplicate imports. The repository I provided is a minimal example: if you remove one of the imports, Jest no longer detects any memory leaks.
This issue occurred to me with the aws-sdk libraries, but it might not be strictly related to them. I could not pinpoint what specific characteristic of the aws-sdk libraries causes this.
Environment
The text was updated successfully, but these errors were encountered: