Fix segfault caused by destruction order of Event and Connection #234
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.
🦟 Bug fix
Fixes gazebosim/gz-sim#906
Summary
A segfault occurs in the destructor of
common::Connection
if thecommon::Event
its associated with has already been deleted. This patch clears theevent
pointer ofcommon::Connection
when the associatedcommon::Event
is deleted.Another issue mentioned in gazebosim/gz-sim#906 is that the destructor of
std::function
crashes if the function it points to is from a shared library that has been unloaded. This is fixed by invoking the destructor as soon ascommon:EventT::Disconnect
is called viacommon::Connection::~Connection
since that's likely to be right before the shared library containing thecommon::Connection
is unloaded.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge