[gstreamer-bugs] [Bug 573823] pad block callback if it is re-blocked while the previous callback is running

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=573823

  GStreamer | gstreamer (core) | Ver: git

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #129886|none                        |committed
               Flag|                            |
 Attachment #129887|none                        |committed
               Flag|                            |
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.23




------- Comment #3 from Wim Taymans  2009-03-09 10:52 UTC -------
sorry, wrong author field here..

commit da0060d3aadb15d6a05812a17c9a32db82c1c4ec
Author: Wim Taymans <wim.taymans at collabora.co.uk>
Date:   Mon Mar 9 11:39:34 2009 +0100

    pad: call new callbacks set in the block callback

    Keep track of when a new callback is installed in the callback and call the
new
    callback in that case.
    Add unit test for checking pad blocking.
    Fixes #573823.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=573823.