[Bug 742684] aggregator: Usage of GCond is racy.

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=742684
  GStreamer | gst-plugins-bad | git

Olivier Crête <olivier.crete> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |739010

--- Comment #1 from Olivier Crête <olivier.crete at ocrete.ca> 2015-01-10 05:08:43 UTC ---
Actually, all of the locking around flushing and seeking is quite dodgy. There
are a bunch of probably useless atomics, where the same variable is read
somewhere else without the atomics. The stream lock is taken in the flush_start
and released on a flush_stop.. But after a flush start, there is no guarantee
you'll get a flush_stop, you could get a state change to NULL instead! I'm not
sure I understand why the duplicated gst_aggregator_pad_steal_buffer() in
flush_start ?

To make it fail:

GST_CHECKS=test_flush_start_flush_stop make elements/audiomixer.forever
GST_CHECKS=test_live_seeking make elements/audiomixer.forever

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