After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 642466 - playbin2: after replacing a video sink with the pipeline in NULL state I still get the old one
playbin2: after replacing a video sink with the pipeline in NULL state I stil...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.30
Other Linux
: Normal normal
: 0.10.33
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 643772 647164 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-02-16 15:02 UTC by Alberto Garcia
Modified: 2011-04-08 13:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test case (3.11 KB, text/x-csrc)
2011-02-16 15:02 UTC, Alberto Garcia 		Details

Description Alberto Garcia 2011-02-16 15:02:31 UTC 
Created attachment 181001 [details]
Test case

In the attached test case I create a playbin2, set a video sink, play
a video for some time, then stop it, set the pipeline to NULL and set
a new video sink to the pipeline.

At this point I'm expecting the old sink to be destroyed and replaced
by the new one, but if I query the pipeline I still get the original
video sink, which by the way increases its reference counter each time
I repeat the process.
Comment 1 Mark Nauwelaerts 2011-02-23 13:39:27 UTC 
Following commit takes care of this.  Note however:
* the new sink only takes effect in later state changes (so querying still reports previous one temporarily)
* increased reference count seems due to the test app not releasing the ref it obtains when querying the property


commit 19052a847d43c489e6bfd249d4e63ba31e630fe1
Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Date:   Wed Feb 23 14:31:13 2011 +0100

    playsink: release all chains when going to NULL
    
    Also fixes #642466.
Comment 2 Alberto Garcia 2011-02-23 14:26:37 UTC 
(In reply to comment #1)
> * increased reference count seems due to the test app not releasing
> the ref it obtains when querying the property

Oops, my bad. Thanks for fixing it!
Comment 3 Lionel Landwerlin 2011-03-06 18:44:08 UTC 
*** Bug 643772 has been marked as a duplicate of this bug. ***
Comment 4 Sebastian Dröge (slomo) 2011-04-08 13:32:31 UTC 
*** Bug 647164 has been marked as a duplicate of this bug. ***