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
ServerGoalHandle should be destroyed before removing. #1113
ServerGoalHandle should be destroyed before removing. #1113
Conversation
Signed-off-by: Tomoya Fujita <Tomoya.Fujita@sony.com> Co-authored-by: Tamaki Nishino <otamachan@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This honestly seems like a good cleanup to me overall. I think it is more logical to track the futures in the ActionServer than in the unrelated ServerGoalHandle.
Woohoo! Is there any chance this might be backported to humble? |
We should probably wait for a while to see if this does not have any regression with rolling, but i think we can do that. CC: @clalancette @sloretz |
Hi! thanks for the fix, Is it possible to create a backport PR for humble so we could try it out? |
@Mergifyio backport humble |
✅ Backports have been created
|
Signed-off-by: Tomoya Fujita <Tomoya.Fujita@sony.com> Co-authored-by: Tamaki Nishino <otamachan@gmail.com> (cherry picked from commit 79ec706)
Hey folks! Any idea when the next |
I guess we do not have concrete date for that so far, last patch was https://discourse.ros.org/t/preparing-for-humble-sync-and-patch-release-2023-05-02/31105. CC: @audrow |
@fujitatomoya: friendly ping? |
@audrow do you happen to know the next patch schedule for humble? |
replace #1070.
This PR addresses the following two issues.
ServerGoalHandle
. (original issue https://answers.ros.org/question/411394/rclpy-action-server-seems-slowing-down-and-consuming-memory-in-long-term/)ActionServer
should own theresult_future
, butServerGoalHandle
. (see Call destroy() before removing ServerGoalHandle #1070 (comment))@otamachan i borrowed your code from #1070, so added you as Co-Author.