-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 (core dumped) problem in tfjs-node #8284
Comments
Hi, @Hyodori04 I apologize for the delayed response and thank you for bringing this issue to our attention, if possible could you please help us with your Github repo along with complete steps to replicate the same behavior from our end to investigate this issue further from our end ? Thank you from your cooperation and patience. |
We serve our serivce as product. So it's hard to share Github repo that provide a reproducible code. Is there any other way to help? |
Hi, I bring core dump gdb backtrace
|
lldb trace
|
System information
Describe the current behavior
We serve our service in docker node.
If there are several sequential requests that use model.predict, our node server is killed
I think there is some kind of memory leak because error logs are like
And docker metrics have similar memory size
Aborted (core dumped)
Describe the expected behavior
Memory leak error doesn't happen
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/CodePen/any notebook.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
And other problem is some version services do not make error
We test using same tool called charles
We use same CD to deploy and same os because we use same docker
We have checked some versions like gcc, python, package.json and they are same
If there is some things to check, comment it and we can give more infomation
The text was updated successfully, but these errors were encountered: