-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
On intel Mac node endless starts new threads and consumes more and more memory until killed. #47697
Comments
Going back to node 18 doesn't work as the project is using yarn3 / berry which i can't get working ... |
Possibly a duplicate of #47566, if so see yarnpkg/berry#5399 (comment) for a workaround. |
Output of Macs Activity Monitor: |
@merceyz Workaround worked for But not for the LSP server started by IntelliJ with: Any ideas for that...? |
i also delete So i assume it really is a duplicate of #47566 and close this (until new developments make me reopen this..) Thanks for the quick response. |
Version
v20.0.0
Platform
Darwin arMBP 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar 6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64 x86_64
Subsystem
mac osx ventura
What steps will reproduce the bug?
starting node from e.g. IntelliJ or "yarn start" from an cra react app.
How often does it reproduce? Is there a required condition?
Evreytime
What is the expected behavior? Why is that the expected behavior?
Should start a few hundred(?) thread and stabilize on that level
What do you see instead?
node start new thread evrey few seconds and consumes more and more memroy until the mac gets sluggy
Additional information
node installed using home brew,
thread are all looking like this )sorry for scrennshot, macs are stupid)
uv__io_poll
looks suspicios:And this is macs activity app with one node from intellij and the other from yarn start:
The text was updated successfully, but these errors were encountered: