-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Memory leak - npm subprocesses #213115
Comments
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
pls let us know what happened with extensions disabled |
Still haven't been able to reliably reproduce the error - it did happen once while I had only ESLint extension enabled, and I ran |
The command in question comes from the builtin npm extension
|
@meganrogge #210601 was added between the two versions. |
Thanks @chrmarti - that's the missing link, I can reliably reproduce the issue now, simply by hovering over a package version in Node version 20.13.1 On one of my PCs exhibiting the issue Node was installed via Volta 1.1.1 (so not corepack enabled), can't check the other install right now but I think it was installed via NVS or similar... |
@stacy-rendall I think the command is missing some of the environment variables I forgot to inherit from the main process and should be fixed by #212856 |
should be already fixed by #213306 |
I can confirm that the issue is no longer occurring in Version: 1.90.0-insider |
closing given it doesn't reproduce in insider's |
Does this issue occur when all extensions are disabled?: TBC
Steps to Reproduce:
npm view --json -- <something> dist-tags.latest homepage version time
, until Task Manager becomes unresponsiveCurrently testing with extensions disabled, will update here if it happens again with extensions disabled.
The text was updated successfully, but these errors were encountered: