You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some google tests which also checks the memory leaks. Tests open basically a session and create a publisher and a subscriber. After the test they should be cleaned up again. For that, I am using :
These memory "leaks" come from rust static variables (namely ZRuntimePool) which are never dropped.
Rust does not drop static variables by design.
We have an API to force-drop ZRuntimePool to prevent corresponding memory leaks from appearing in the logs, but it is only available in zenoh-rust. We will likely provide similar api for zenoh-c/zenoh-c++ for the next release.
@hguelle If possible, could you check the dev/1.0.0 version and call zc_stop_z_runtime() at the end of your program and let us know if you still get memory leaks reported.
Describe the bug
I have some google tests which also checks the memory leaks. Tests open basically a session and create a publisher and a subscriber. After the test they should be cleaned up again. For that, I am using :
These are all returning 0 as ret val. But after the test
To reproduce
memory_leaks.txt
System info
Debian x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: