[WIP] Investigation on leaks #326
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Sink-related elements
joaoantoniocardoso
force-pushed
the
better_tasking_less_locks_WIP
branch
from
d789d23
to
369e79d
Compare
joaoantoniocardoso
force-pushed
the
better_tasking_less_locks_WIP
branch
from
369e79d
to
e31281a
Compare
joaoantoniocardoso
force-pushed
the
better_tasking_less_locks_WIP
branch
from
e23182b
to
f1229ea
Compare
Closed
|
Closed as all interesting parts of the work were already merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With this group of commits, it seems that the leaks are from inside GST. Maybe we are not finishing it correctly, maybe we are keeping references around, like a pad/element/pipeline clone