hlssink2: Don't assert if we don't have a current location when receiving the...
hlssink2: Don't assert if we don't have a current location when receiving the fragment-closed message
This can happen if the application did not provide an output stream for the fragment and didn't handle the error message before splitmuxsink decided to consider the fragment closed.
Merge request reports
Activity
Please register or sign in to reply