[Bug 774241] vaapi: fix failures of gst-validate-launcher TCs

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=774241

--- Comment #1 from Hyunjun Ko <zzoon at igalia.com> ---
Problem 1: Failures of all TCs with "intensive_state_change" scenario

Most tcs with intensive_state_change scenario lead to failure as following.
gst_vaapi_window_get_size: assertion 'window != NULL' failed, or deadlock
sometimes.

Callstack is following.

#0  0x00007ffff6fbfa6b in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007ffff6fbfbdf in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffa123c4d8 in gst_vaapisink_reconfigure_window
(sink=sink at entry=0x7fffc807a9f0) at gstvaapisink.c:899
#3  0x00007fffa123f4c5 in gst_vaapisink_x11_handle_events (sink=0x7fffc807a9f0)
at gstvaapisink.c:429
#4  0x00007fffa123c012 in gst_vaapisink_event_thread (sink=0x7fffc807a9f0) at
gstvaapisink.c:918
#5  0x00007ffff6fdfbc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007ffff6d596fa in start_thread (arg=0x7fffba7fc700) at
pthread_create.c:333
#7  0x00007ffff6a8fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

This occurs because the xevent thread is not destroyed when the pipeline shuts
down.
Currently, when the vaapisink element is destroyed, the thread is destroyed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.