Unref events which are not accepted #150
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In one of our automated tests we had the following situation: a pipline which fed (H264) buffers into an interpipesink was started. Right after that we started a second pipeline which consumed these buffers via an interpipesrc. When doing this the GStreamer leak tracer reported some leaked tag events. Introducing a short wait between starting the two pipelines would remove the leak.
It seems that the leaked events arrive at the second pipeline while the (second) pipeline is not able to accept them (because it is still starting up?). The intention of this PR is to unref the events in such a situation.