[Bug 753622] splitmuxsink: do not destroy the multiqueue & muxer when going to NULL

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=753622

--- Comment #7 from George Kiagiadakis <george.kiagiadakis at collabora.com> ---
Looking at this again, you are right that reset() cannot be done in
NULL->READY. In fact it is not acceptable to reset as long as there are request
pads alive. My new approach now will call reset() as soon as all request pads
are released, or in READY->NULL if no pads were ever requested.

I also extended the unit test to showcase the bug when the patch is not
applied.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.