[Bug 721289] New: gstpad: using multiple blocking probes doesn't work as expected

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=721289
  GStreamer | gstreamer (core) | git

           Summary: gstpad: using multiple blocking probes doesn't work as
                    expected
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: todd at agulnick.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Here's a scenario:

Add blocking Probe A.
Probe A's callback gets invoked and returns GST_PAD_PROBE_OK, leaving the block
in place.

Add blocking Probe B.
Probe B's callback doesn't get invoked, as pad is already blocked.

Remove blocking probe A.
Probe B's callback still doesn't get invoked.

Pad remains blocked because of Probe B's existence, but the callback associated
with the Probe B was never invoked.

A more desirable implementation would track which probe had blocked the pad (in
the example above, that would be Probe A). When that pad is removed, it
unblocks and invokes the callback of any remaining blocking probes (in this
example, Probe B). If the callback leaves the blocking probe in place, then
Probe B becomes the de facto blocker and the pad remains blocked until it is
removed.

-- 
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.