[gstreamer-bugs] [Bug 612735] New: Changing state play-null-play on pipelines created by gst_parse_launch crashes

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=612735
  GStreamer | gstreamer (core) | 0.10.x

           Summary: Changing state play-null-play  on pipelines created by
                    gst_parse_launch crashes
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.x
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: ayd011 at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Created an attachment (id=156005)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=156005)
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"

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.