Repository navigation
Remove stale MessageMemoryPool TODO from the executor - #3374
Merged
Merged
Conversation
The TODO said that MessagePoolMemoryStrategy could return a message to the pool while a callback still holds a shared_ptr to it. That was fixed by ros2#2336, which returns pool slots from the shared_ptr deleter once nothing else references the message and left return_message() empty. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: mini-1235 <mauricepurnawan@gmail.com>
ABI Compliance Check✅ Verdict: compatible
✅
|
ahcorde
approved these changes
Oct 26, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
I was reading this part of the code today and was a little confused by the TODO here. In particular, it looks like #2336 already addressed this by making
MessagePoolMemoryStrategy::return_message()a no-op and returning the message to the pool through a custom deleter only after all shared pointers have been released. Thus, I think the TODO here is outdated.Is this user-facing behavior change?
No, comment only change
Did you use Generative AI?
Yes, Claude Opus 5.5 to discuss the code with me
Additional Information