-
Notifications
You must be signed in to change notification settings - Fork 118
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
Keep reference to DomainParticipantFactory
#770
Keep reference to DomainParticipantFactory
#770
Conversation
8951c44
to
73f7936
Compare
rmw_fastrtps_shared_cpp/include/rmw_fastrtps_shared_cpp/custom_participant_info.hpp
Show resolved
Hide resolved
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.
@MiguelCompany thanks for the explanation, lgtm with green CI.
73f7936
to
94cffad
Compare
@fujitatomoya @ahcorde I rebased this one to get the changes from #763 (I think the test failures were due to that) |
Ah, CI isn't working because this needs to be rebased. @MiguelCompany can you do that? |
Signed-off-by: Miguel Company <[email protected]>
Signed-off-by: Miguel Company <[email protected]>
94cffad
to
8851bfd
Compare
Done! |
The failures here are all in known flakes, so going ahead and merging this. |
@clalancette @fujitatomoya Should we backport this? |
@MiguelCompany i say we should especially for jazzy and humble, but this is breaking ABI change? |
@fujitatomoya Strictly speaking, this is an ABI break. But since it is on the internal package |
BTW, it cannot be backported to Humble, because |
@MiguelCompany i am okay with backport for jazzy, lets hear from other opinion. |
If this hasn't yet been backported, I would really appreciate a backport to Jazzy. |
@clalancette what do you think about backporting jazzy? IMO, this should be no problem and better bug fix for jazzy LTS. |
I'm not entirely sure, but I think this may be involved in what is causing our crashes on RHEL with flake8. I'm still debugging that, but commenting out the call to Thus I think we should hold off on backporting this until we figure out what that problem is. |
We've seen several issues related with destruction order lately.
This PR aims to mitigate them by leveraging Fast DDS
DomainParticipantFactory::get_shared_instance()
.It should then avoid the automatic destruction of the factory (and the participants it created) until all the contexts in the process have been destroyed.
This can be backported to Jazzy and Iron, but not Humble, since
get_shared_instance()
is only available from Fast DDS 2.8.0 onwards.