[gstreamer-bugs] [Bug 339326] pads not set to FLUSHING when created

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=339326
 GStreamer | gstreamer (core) | Ver: HEAD CVS


Edward Hervey changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bilboed at bilboed.com
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1




------- Comment #1 from Edward Hervey  2006-07-09 13:43 UTC -------
Example where it causes issues:

* An element creates a New pad (not activated, flushing) in READY.
* Someone does a gst_pad_set_blocking(newpad, TRUE, callback)
* The element's state is set to lock (gst_element_set_locked_state (TRUE))
* we switch the element's state to PAUSED, which puts it to PAUSED without
calling the state_change function (and the pad activation).
* We unblock the state (gst_element_set_locked_state (FALSE))
* We change the state of the element to READY
** The state_change function tries to deactivate the pad, but since it's
already not-activated, it won't call the function that unsets the FLUSHING flag
** The element send an EOS
** The pad blocks
*** LOCKS in state_change


-- 
Configure bugmail: http://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.