aggregator: Use src_lock to protect latency related members
authorOlivier Crete <olivier.crete@collabora.com>
Fri, 20 Feb 2015 02:21:56 +0000 (21:21 -0500)
committerTim-Philipp Müller <tim@centricular.com>
Sat, 2 Dec 2017 15:10:26 +0000 (15:10 +0000)
commit5ac166a5d9ead73bd2bce67fe854ed5d13dfa276
tree8ebb90f75005b7f8538a574740a0b6f7597c6d78
parent77698267dbbf6eafcf86daae495bcb901c0656d6
aggregator: Use src_lock to protect latency related members

One has to use the src_lock anyway to protect the min/max/live so they
can be notified atomically to the src thread to wake it up on changes,
such as property changes. So no point in having a second lock.

Also, the object lock was being held across a call to
GST_ELEMENT_WARNING, guaranteeing a deadlock.
libs/gst/base/gstaggregator.c