Remove clear request callback in service destructor #143
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remove clear_on_new_request_callback from service destructor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When using lifecycle nodes, the node creates services from an rcl service handle owned by the node's rcl state machine, not the service itself. Because the EventsExecutor also clears the service callbacks manually in its destructor, there is a segfault that occurs depending on the order of destruction if the rcl/rmw service handle is destroyed underneath before the callback has been removed.
From what I can tell, this clear is unnecessary in the service destructor. This clear is also not in the upstream rclcpp.
I tested this change on a local unit test that adds a lifecycle node to an events executor (also a SingleThreadedExectutor) and it passes.