Unregister typesupport rather than delete #416
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a use-after-free that I discovered while adding fault injection tests to rcl_action over at ros2/rcl#730. Somehow rcl_action's typesupport for its client and subscription were being duplicated. When it was cleaned up during this fail block in create_subscription, it would try to delete it again over in rmw_client_fini. Instead, I believe it needs to unregister it, which also deletes it, so that it won't get deleted twice.
rmw_client.cpp
already does this with unregister rather than deleting the pointer directly.Before-and-after unit tests will have to wait until tomorrow.
Signed-off-by: Stephen Brawner [email protected]