[Bug 721300] tee: locking issues
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Thu Jan 2 02:19:21 PST 2014
https://bugzilla.gnome.org/show_bug.cgi?id=721300
GStreamer | gstreamer (core) | git
Sebastian Dröge (slomo) <slomo> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
Target Milestone|HEAD |1.3.1
--- Comment #3 from Sebastian Dröge (slomo) <slomo at coaxion.net> 2014-01-02 10:19:15 UTC ---
This should fix it, please reopen otherwise (and if it fixes the problem I will
backport to 1.2):
commit 34f8b4d6f3e6a61519f23e8ef0644a6fdfc99daa
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Thu Jan 2 11:13:27 2014 +0100
tee: Remove dyn lock
It was used for pad-alloc in 0.10 but currently is completely unused
and not necessary. All pad access is protected by the tee object lock
and keeping another reference to the current pad.
commit e80fd39947c697d591789feee918cd6a27f1ca15
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Thu Jan 2 11:09:59 2014 +0100
tee: Keep another ref to our one and only srcpad around while pushing
A pad probe on that pad might otherwise just release the pad, drop
the last reference and cause great misery.
https://bugzilla.gnome.org/show_bug.cgi?id=721300
--
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.
More information about the gstreamer-bugs
mailing list