-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
Possible memory leak in node v4.2.3 #4347
Copy link
Copy link
Closed
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.memoryIssues and PRs related to the memory management or memory footprint.Issues and PRs related to the memory management or memory footprint.vmIssues and PRs related to the vm subsystem.Issues and PRs related to the vm subsystem.
Description
Metadata
Metadata
Assignees
Labels
duplicateIssues and PRs that are duplicates of other issues or PRs.Issues and PRs that are duplicates of other issues or PRs.memoryIssues and PRs related to the memory management or memory footprint.Issues and PRs related to the memory management or memory footprint.vmIssues and PRs related to the vm subsystem.Issues and PRs related to the vm subsystem.
There's an interesting possible problem when upgrading from node 0.10 to node 4: It seems like running code via
vm.runInNewContextretains the whole context, including all native constructors, globals, etc.. From our current testing it looks like those are never collected even after nothing in our app code holds a reference to any object belonging to the context, leading to the process running out of memory eventually. After we stopped usingvm.runInNewContext, the problem went away.As mentioned above, we have only circumstantial evidence that the leak is in
vm.runInNewContextitself.