[Bug 721096] pad: Pad BLOCKING probe callback issues

[GStreamer (bugzilla.gnome.org)]

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

--- Comment #5 from Wim Taymans <wim.taymans at gmail.com> 2013-12-30 09:56:27 UTC ---
If there are multiple threads all doing things on the pad, the probe will be
called multiple times from these multiple threads. GStreamer does not try to
serialize the probe callbacks because that would always create a bottleneck. If
the app can't deal with concurrent probe callbacks, it needs to serialize
itself, like:

 int id;

 probe_callback () {
   mutex_lock()
   if (id != 0) {
     /* do stuff */
     ....
     remove_probe (id)
     id = 0;
   }
   mutex_unlock()
 }

 id = add_probe()

Simply checking if the probe was not removed when the callback is called should
be enough.

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