Skip to content

rtspsrc: fix invalid seqnum assertions

Mathieu Duponchelle requested to merge meh/gstreamer:rtspsrc-fix-assert into main

Upon fatal errors the loop function will first post an error message then push out an EOS event.

An application may react immediately to the error message by setting the state of the pipeline to NULL, meaning by the time we push out the EOS event PAUSED_TO_READY may have reset the seek seqnum to -1.

While this is harmless, the assertion when setting an invalid seqnum isn't tidy, fix this by simply not resetting to INVALID as it serves no practical purpose and the next READY_TO_PAUSED will select a new seqnum anyway.

Merge request reports