[Bug 742684] aggregator: Usage of GCond is racy.
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Wed Jan 14 14:13:29 PST 2015
https://bugzilla.gnome.org/show_bug.cgi?id=742684
GStreamer | gst-plugins-bad | git
--- Comment #8 from Olivier CrĂȘte <olivier.crete at ocrete.ca> 2015-01-14 22:13:25 UTC ---
Made some more progress, it seems the audiomixer tests are racy as they expect
the flush_stop to be synchronous, but it's not anymore. Also, the use case
where you have a gst_element_release_pad() called in the middle of a flushing
seek is not well handled now.
Example problematic use-case:
- upstream flushing seek and forward it upstream to sink_0 and sink_1
- get a flush start on pad sink_0
- get a flush start on pad sink_1
- get a flush stop pad sink_0
- release pad sink_1
- .. the streaming never restarts because the second flush stop never happens
Also, it seems that locking around gst_pad_remove() is not sufficient and then
we get memory corruption and or that something ues the pads without taking the
element's object lock and don't keep a reference. The investigation continues.
--
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