[gstreamer-bugs] [Bug 514717] memleak in Pad.set_blocked_async()

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

  GStreamer | gst-python | Ver: HEAD CVS

Alessandro Decina changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #122363|0                           |1
        is obsolete|                            |




------- Comment #12 from Alessandro Decina  2008-11-14 17:31 UTC -------
Created an attachment (id=122673)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=122673&action=view)
gst_pad_set_blocked_async_full + tests

We discussed this a bit with wtay on irc and he gave me some suggestions
(destroy user_data in gst_pad_dispose if necessary and don't call destroy
when resetting user_data to the same value). I also added some tests.

We also agreed in that the current implementation is broken when 
gst_pad_set_blocked_async (pad, state, ...) is called and GST_PAD_IS_BLOCKED
(pad) == state. The only problem is that the behaviour is sort of documented in
the API. Anyway, I added a test (disabled for the moment) which shows what I
think the correct behaviour should be. If people think it can be changed, i'm
going to enable the test and change the implementation.


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