René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"SourceTextModule memory leak","articleBody":"\u003c!--\r\nThank you for reporting an issue.\r\n\r\nThis issue tracker is for bugs and issues found within Node.js core.\r\nIf you require more general support please file an issue on our help\r\nrepo. https://github.com/nodejs/help\r\n\r\n\r\nPlease fill in as much of the template below as you're able.\r\n\r\nVersion: output of `node -v`\r\nPlatform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)\r\nSubsystem: if known, please specify affected core module name\r\n--\u003e\r\n\r\n* **Version**: v14.2.0\r\n* **Platform**: Darwin Kernel Version 19.4.0\r\n* **Subsystem**: vm\r\n\r\n### What steps will reproduce the bug?\r\nrun this snippet with --experimental-vm-modules\r\n```js\r\nconst {SourceTextModule} = require('vm');\r\n\r\nlet grow = () =\u003e {\r\n  new SourceTextModule(`1 + 1`);\r\n  setTimeout(grow, 100)\r\n}\r\n\r\ngrow()\r\n```\r\n### How often does it reproduce? Is there a required condition?\r\nReproducible on every run on my machine. \r\n### What is the expected behavior?\r\nSourceTextModule should be cleaned up by GC\r\n\r\n### What do you see instead?\r\nThe SourceTextModule instances never get cleaned up.\r\n![image](https://user-images.githubusercontent.com/19875911/82128723-78d41700-97bd-11ea-9fc3-565a596a5357.png)\r\n\r\n### Additional information\r\n\r\nI think issue is that ModuleWrap is used as a key in WeakMap in vm module, but I am not really familiar with this codebase.\r\n","author":{"url":"https://github.com/grosto","@type":"Person","name":"grosto"},"datePublished":"2020-05-16T19:51:55.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":15},"url":"https://github.com/33439/node/issues/33439"}