[gstreamer-bugs] [Bug 570910] Removing the target of a ghostpad does not re-target the ghostpad to NULL

[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=570910

  GStreamer | gstreamer (core) | Ver: git

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #128198|none                        |committed
               Flag|                            |
 Attachment #128199|0                           |1
        is obsolete|                            |
 Attachment #128319|0                           |1
        is obsolete|                            |
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.23




------- Comment #5 from Wim Taymans  2009-02-16 11:59 UTC -------
commit 26f368f7e751661d53895f8c00b07bb13486bffa
Author: Wim Taymans <wim.taymans at collabora.co.uk>
Date:   Mon Feb 16 12:58:34 2009 +0100

    Clear target when the target pad disappears

    When the target pad disappears (because it was explicitly unlinked or the
    element was removed/unreffed) make sure we receive a notify with the unlink
    function on the proxy pad and clear the target. We use a simple flag to not
do
    this and cause deadlocks when the target was changed explicitly using the
    ghostpad functions.

    Update the unit test because we now unref the target sooner (and
correctly).


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