Handle socket closed by client before start of stream arrives in RTMP Source Bin #87
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.
I had a flow in my application where the client was closing the socket before the start of stream was being sent. That was causing the RTMP source to send a message
:unexpected_socket_closed
to the parent, which in my case is the RTMP Source Bin. https://github.com/membraneframework/membrane_rtmp_plugin/blob/v0.22.1/lib/membrane_rtmp_plugin/rtmp/source/source.ex#L228This message is not being handled by the bin so it causes a crash in my application. I have added handling for this case and decided to send the message to the bin's parent.