-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Nats microservice memory leak #5431
Labels
needs triage
This issue has not been looked into
Comments
Also created bug in repo Node.js nodejs/node#35228 |
Closing issue due nodejs/node#35048 |
This was referenced Jun 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Current behaviour
So, I have detected memory leak in my nats nest service
After some research I found, that problem is not in my code.
Actually the problem is in https://github.com/nestjs/nest/blob/master/packages/microservices/server/server.ts#L173
As
pattern
in NATS always string, then every request code is failing to parsepattern
and it leads to a memory leakI don't know why this construction is leaking, but it is. I found the same issue on the StackOverflow https://stackoverflow.com/questions/48309464/node-js-try-catch-memory-leak
Reproduction in CodeSandbox: https://codesandbox.io/s/restless-leaf-gtyn1?file=/src/index.js
Environment
The text was updated successfully, but these errors were encountered: