Take listeners_lock for g_hash_table_foreach operations on listeners. #117
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.
Fix for #116
Need to take a lock when accessing listeners hash table because listeners can be removed by other threads. Must use a recursive mutex because the notify calls can then come back and call gst_inter_pipe_leave_node() or gst_inter_pipe_add_node() which results in a 2nd attempt to lock the listeners mutex in the same thread.