-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
v20.0.0 Unlimited increase in memory #47761
Comments
Please provide detailed and accurate step-by-step instructions so that we can try to reproduce the issue.
If it exceeds the size of the physical RAM, then it can't be the RSS that you are describing. Please provide more information on the kind of memory usage you are observing. |
Possibly a duplicate of #47566. |
There is no problem with v18.16.0, v20.0.0 yarn create vue, created, port and memory in top have been rising, and finally up to 20G +。 |
@KanLai without steps to reproduce this is not an actionable bug report. Either provide said steps or close the issue. |
@bnoordhuis @tniessen |
Can you just post the steps here? Aside: please test with the official binary from nodejs.org, not the one provided by homebrew. |
Also suffering from this. Brew binary. Using yarn 3 and parcel 2.8.0 on macOS ventura 13.2.1 (22D68). Happens both on my intel hackintosh and M1 MBP. I think it's not only growing RAM like crazy but also opening an insane amount of file descriptors. When I do lsof there's a never ending list and on my M1 MBP the systam ran out of file descriptors until I killed all node processes and everything in the system that needed to open files failed. Downgrading to node 19.9.0 with nvm untill this is fixed. |
|
Do you consider the binaries that nvm installs official? Because I don't want to run your .pkg installer that can write files to anywhere which are hard to uninstall. That's why I use brew.30 apr. 2023 kl. 12:23 skrev Ben Noordhuis ***@***.***>:
Brew binary
#47761 (comment)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Yes, nvm should be downloading official binaries from nodejs.org. |
I can confirm that I can reproduce this behavior even with the latest official node, installed via nvm. Steps to reproduce:
Lsof output:/private/tmp/parcel-tree-shaking-bug After some time the system will even start acting up, like:
|
Can you reproduce on 20.1.0? |
appears to be fixed in v20.1.0 |
Thanks for confirmation |
seeing an increase in CPU usage in Node LTS (v20.10.0) in a high traffic application at my work |
Version
v20.0.0
Platform
MacOS 13.3.1
Subsystem
No response
What steps will reproduce the bug?
No response
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
I used brew to install node, and then brew update, node became v20.0.0, entered the existing project, memory has been growing, testing. Yarn 3. 5 creates the vue project, executes yarn create vue, and then enters the project, and the memory grows until my 32 gigabytes of memory runs out and then grows.
Additional information
No response
The text was updated successfully, but these errors were encountered: