-
Notifications
You must be signed in to change notification settings - Fork 95
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: meta objects not destroyed #131
Comments
I created a minimal demo: https://github.com/agutenkunst/leak_demo_pkg |
I second I've experienced this too. I get a flood of these when using moveit building with address sanitizer. I tried looking through the code to see if I can understand what I should be doing to fix this but I can't figure it out. |
Signed-off-by: y-okumura <y-okumura@isp.co.jp>
According to these comments the whole problem boils down to the basic decision whether the library should
The library went with the former option and we are stuck with unfreeable memory as a result. |
to work around ros/class_loader#131 and have all code using the `CurrentState` stage sanitize correctly (unless they use it through ClassLoader).
to work around ros/class_loader#131 and have all code using the `CurrentState` stage sanitize correctly (unless they use it through ClassLoader).
to work around ros/class_loader#131 and have all code using the `CurrentState` stage sanitize correctly (unless they use it through ClassLoader).
Using the ClassLoader (version
0.4.1
) via pluginlib as recommended, we could detect some memory leaks.My guess is that metaobjects are not destroyed after they have been inserted into the "graveyard". Or did I miss something here?
Could be related: ros/pluginlib#126
See the log below. It would be nice to get another opinion.
Excerpt of log.txt:
The text was updated successfully, but these errors were encountered: