We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi! We noticed a memory leak when using watch Repo for debug: https://github.com/Snowman2908/node-foundationdb-watch-memory-leak
watch
Starting profiling:
app-1 | $ /node_modules/.bin/ts-node index.ts app-1 | NodeJS heap: 94.99MB app-1 | Process memory: 290.81MB app-1 | NodeJS heap: 99.58MB app-1 | Process memory: 305.81MB app-1 | NodeJS heap: 102.77MB app-1 | Process memory: 321.31MB app-1 | NodeJS heap: 105.6MB
End profiling after 10 min:
app-1 | Process memory: 949.81MB app-1 | NodeJS heap: 95.78MB app-1 | Process memory: 963.19MB app-1 | NodeJS heap: 97.89MB app-1 | Process memory: 976.06MB app-1 | NodeJS heap: 97.07MB app-1 | Process memory: 988.94MB app-1 | NodeJS heap: 96.43MB app-1 | Process memory: 1002.56MB app-1 | NodeJS heap: 100.89MB app-1 | Process memory: 1016.69MB
The situation is similar to what happened with tn, NodeJS heap size stays at consistent levels, but the total process memory grows
tn
I use macOS with rosetta, but we have the same situation with a memory leak in our services in Kubernetes
The text was updated successfully, but these errors were encountered:
Moved from #48
Sorry, something went wrong.
Thanks for the repro! That makes this much less daunting to find & fix. I'll take a look next week. I've been busy with some other work.
Hi @josephg! I understand correctly that you will release it next week, when will you have free time?
Successfully merging a pull request may close this issue.
Hi! We noticed a memory leak when using
watch
Repo for debug: https://github.com/Snowman2908/node-foundationdb-watch-memory-leak
Starting profiling:
End profiling after 10 min:
The situation is similar to what happened with
tn
, NodeJS heap size stays at consistent levels, but the total process memory growsI use macOS with rosetta, but we have the same situation with a memory leak in our services in Kubernetes
The text was updated successfully, but these errors were encountered: