Simon Farnsworth d946e7972e Work around ABBA deadlock between vaapisink and vaapipostproc ... vaapisink takes the display lock, then does a gst_buffer_replace which can take the lock on the gst_vaapi_video_pool. vaapipostproc asks the gst_vaapi_video_pool for a new surface. This takes the lock on the gst_vaapi_video_pool; if you're unlucky, there are no free surfaces, which means that gst_vaapi_surface_create is called. gst_vaapi_surface_create takes the display lock. If vaapisink and vaapipostproc are in different threads, and this happens, you get a deadlock. vaapisink holds the display lock, and wants the gst_vaapi_video_pool lock. vaapipostproc holds the gst_vaapi_video_pool lock and wants the display lock. Work around this by releasing the display lock in vaapisink around the gst_buffer_replace. https://bugzilla.gnome.org/show_bug.cgi?id=738249 Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk> Signed-off-by: Sreerenj Balachandran <sreerenj.balachandran@intel.com>		2015-06-29 13:10:15 +03:00
..
vaapi	Work around ABBA deadlock between vaapisink and vaapipostproc	2015-06-29 13:10:15 +03:00
Makefile.am	build: use git.mk	2015-05-18 16:14:46 +02:00