-
-
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]: False positive memory leak when running with --experimental-vm-modules
and using --detectLeaks
#14649
Comments
--experimental-vm-modules
and using --detectLeaks
--experimental-vm-modules
and using --detectLeaks
Seems like it's not only Jest, I've implemented the leak detector and tested pure Node (https://github.com/enisdenjo/node-leak). Running an ESM script in the vm leaks, while CJS script doesn't. 🤔 |
See #14526 and its linked upstream Node comment (about how it's not really possible to create a good leak detector from JS). Dunno if it helps in this case - the point is more that it's inherently not possible to get 100% precise. Node has had some ESM Might be worth opening an issue upstream and pinging |
Opened an issue with Node (nodejs/node#50964). Let's see. |
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
Expected behavior
No leak. Or at least consistent behaviour between CJS and ESM.
Actual behavior
Leaks in ESM, doesn't leak in CJS.
Additional context
Exact same test leaks with:
but doesn't leak with:
Environment
The text was updated successfully, but these errors were encountered: