Replies: 3 comments 1 reply
-
As I pointed out in #1828, most memory leaks happen inside TensorFlow. I agree |
Beta Was this translation helpful? Give feedback.
1 reply
-
I tried to free
I don't understand what's wrong with protobuf. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Resolved in #3223. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am dealing with integration to CP2K from DeePMD-kit. With C interface released, there is now a rather easy way to get them altogether.
While everything seems to be OK with
ssmp
version, insdbg
version (with-fsanitize=leak
to detect possible memory leak), it always run into anEXIT
issue, showing there is still memory leaking. (cp2k/cp2k#3145)By compiling DeePMD-kit C interface also with
-fsanitize=leak
by adding the following intoCMakeLists.txt
, we finally found the leak is due to some implementation of C interface or even deeper dependencies like tensorflow.add_compile_options(-fsanitize=leak -g) add_link_options(-fsanitize=leak)
Logs of regression test for
sdbg
versionI found a few implementation of
new xxx
when creating a pointer, like this inc_api.cc
:Is it safe and might it be the reason of memory leaking?
Beta Was this translation helpful? Give feedback.
All reactions