gstreamer/subprojects/gst-plugins-bad/tests
Alexander Slobodeniuk 0cb12db96c 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/6702>
2024-04-20 20:49:34 +00:00
..
check d3d11device: protect device_lock vs device_new 2024-04-20 20:49:34 +00:00
examples examples: set perfect-timestamp=true on opusenc 2024-04-03 11:35:08 +00:00
files bad: Added W3C Media Source Extensions library 2023-11-19 13:48:43 +00:00
interactive bad/soundtouch: Fix interactive test build on MSVC 2022-09-22 07:20:45 +00:00
validate autovideoconvert: Handle passing bin description instead of factories 2024-01-31 11:00:24 +00:00
meson.build gstreamer-full: add full static support 2023-05-31 15:17:11 +00:00