-
Notifications
You must be signed in to change notification settings - Fork 153
Fix memory leaks #213
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
Comments
FYI @ros2-rust/dev Thanks for the report! Nevermind, I should have read your description more closely. We do have a corresponding |
Does this mean that there's potentially a leak in ROS 2? Or am I misreading this? |
I ran the C++ talker/listener demo from Rolling in Valgrind and saw no memory leaks. But I'm also not seeing any memory leaks when I run the
Which ROS distribution are you using, @Nizerlak? |
I'm using Foxy. |
Hey, I ran valgrind on the unit tests with ros2-foxy on the latest main commit 087527e with the latest Valgrind-3.21.0.GIT and there are no losses reported. Therefore, I recommend to close this ticket.
Interesting find is that Valgrind-3.15.0 available in the
However, this usage of the statx is not reported any more as an error in newer Valgrind versions. See here and here |
@ThomasHauth Thanks for following up on this issue! Yes, we can close it then. |
Recently I've run lib unit tests with valgrind for my PR purposes and I've come across some memory leaks in rclrs lib. Here is full report:
Example places where leak occurs: context.rs, subscription.rs, node.rs.
Seems like deallocation is currently not utilized. For every
rcl_init
call there should be correspondingdeallocate
fromrcl_allocator
.The text was updated successfully, but these errors were encountered: