Disable DataReader on destruction [12870] #2313
Merged
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.
This PR disables the
DataReader
on destruction. This is because, as reported in #2307 , it could be the case that a data sample is received while deleting aDataReader
, which before could end up in a situation in which the underlyingRTPSReader
was accessed when it had been already deleted. To avoid this case, the first thing done on the destruction of theDataReader
is to disable it, which sets theDataReader
andRTPSReader
listeners tonullptr
, thus preventing receiving a data sample on upper layers.Closes #2307