Alexander Slobodeniuk 926d5366b9 d3d11device: protect device_lock vs device_new ... It seems that when D3D11CreateDevice collides in time with other D3D11 calls, in particular the proccess of creating a shader, it can corrupt the memory in the driver. D3D11 spec doesn't seem to require any thread safety from D3D11CreateDevice. Following MSDN, it is supposed to be called in the beginning of the proccess, while GStreamer calls it with each new pipeline. Such crashes in the driver were frequently reproducing on the Intel UHD 630 machine. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/6686>		2024-04-20 11:22:41 +00:00
..
gst	d3d11device: protect device_lock vs device_new	2024-04-20 11:22:41 +00:00
meson.build	Move files from gst-plugins-bad into the "subprojects/gst-plugins-bad/" subdir	2021-09-24 16:14:36 -03:00