GNOME Bugzilla – Bug 612735
Changing state play-null-play on pipelines created by gst_parse_launch crashes
Last modified: 2010-08-19 11:27:07 UTC
Created attachment 156005 [details] Parse application sample to reproduce error changing state through play-null-play Hi, Changing state (play-null-play) crashes on pipelines created by gst_parse_launch. This occurs specifically on pipelines that need dynamic pads to work.The pipeline works only once. When discussed on IRC, was told me that gst_parse_launch() does a lot of 'magic' things under the hood which are hard to reset properly, so a work around would be to throw away the pipeline and create a new one. However, it is still a limitation, that it should be fixed at some point. The attachment is a C application which receives the pipeline description as a parameter, it creates a pipeline using the gst_parse_launch() and initializes a timer, which waits 6 seconds to change the pipeline state from null to play and backwards. It could be helpful if you want to reproduce the error. To run 'gst-parse-app': ./gst-parse-app "<pipeline-description>" Ex: ./gst-parse-app "filesrc name = src location = some.m4a ! qtdemux ! decodebin ! audioconvert ! alsasink"
There are some problems, like you described, with gst_parse_launch. But I can't get it to crash with your sample application. Please provide a backtrace of such a crash, maybe this can be fixed easily :)
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!