This repository was archived by the owner on Oct 7, 2021. It is now read-only.
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 patch fixes some of the memory leaks seen when running the
demo_nodes_cpp
talker
/listener
.But there seem to be several more - mostly inside OpenSplice, e.g. the following - maybe @michielb-prismtech has an idea if we are using the API wrong anywhere:
The call to
tsMetaHolder->create_datawriter
(https://github.com/osrf/opensplice/blob/0941db497e2952ddf69454442071e92e0e69d942/src/api/dcps/c%2B%2B/common/code/Publisher.cpp#L257) inPublisher::create_datawriter
allocates memory.But the corresponding call to
deinit
(https://github.com/osrf/opensplice/blob/0941db497e2952ddf69454442071e92e0e69d942/src/api/dcps/c%2B%2B/common/code/Publisher.cpp#L375) inPublisher::delete_datawriter
seems to never deallocate the memory hence the leak shown in valgrind: