Thiago Santos 4a3f06885a pad-monitor: add lots of locking ... When handling elements that spawn multiple threads (hardware enc/decoders), the pad monitor has to protect its variables specially because some checks involve iterating over internally linked pads to add/get some data for comparison (expected events, timestamp ranges, caps). Aside from locking its own mutex, the pad monitor can also lock the parent's mutex when it needs to use data from its internally linked pads. The locking order should always be parent and then individual pad-monitor mutexes. This should prevent deadlocks when multiple pad-monitors from the same element start doing checks at the same time from different threads.		2013-07-24 16:16:07 -03:00
..
qa	pad-monitor: add lots of locking	2013-07-24 16:16:07 -03:00
Makefile.am	qa: adds gst-qa binary and basic classes to run the QA tests	2013-07-09 16:08:30 -03:00