NULL State Synchronization

Sebastian Dröge sebastian at centricular.com
Fri Sep 2 06:29:15 UTC 2016


On Thu, 2016-09-01 at 13:51 -0700, ht techdev wrote:
> Hi
> On gstreamer 1.4.5, running on Centos 7.2, I have a use case that I am not sure I am handling/understanding correctly:
> 1-      Application start a pipeline, i.e., sets the state to PLAY
> 2-      After an arbitrary amount of time, it sets the state to NULL
> 3-      Current Problem:
> a.       A decoder plugin just prior to pushing its frame, after NULL state , attempts to allocate output frame, which it fails and consequently issues a GST_ELEMENT_ERROR
> b.      This in turn stops the main application, as we are tripping on error messages
> Question is, whether it is the plugin responsibility to block inside _stop, till current frame is processed, or gstreamer is responsible for such synchronizations.

Which decoder plugin is that? That would be a bug in that decoder or
one of the base classes.

Can you send a debug log with GST_DEBUG=6 of this, but first of all try
with a newer GStreamer version? 1.4 is already quite old and this might
already be fixed.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 931 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160902/4b86b5cb/attachment.sig>


More information about the gstreamer-devel mailing list