Seungha Yang 62aa802d17 d3d11bufferpool: Fix heavy CPU usage in case of fixed-size pool ... There's no reason to release GstMemory manually at all. If we do release GstMemory, corresponding GstBuffer will be discarded by GstBufferPool baseclass because the size is changed to zero. Actual cause of heavy CPU usage in case of fixed-size pool (i.e., decoder output buffer pool) and if we remove GstMemory from GstBuffer is that GstBufferPool baseclass is doing busy wait in acquire_buffer() for some reason. That needs to be investigated though, discarding and re-alloc every GstBuffer is not ideal already. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/4943>		2023-07-11 23:23:12 +00:00
..
check	d3d11bufferpool: Fix heavy CPU usage in case of fixed-size pool	2023-07-11 23:23:12 +00:00
examples	example: vaenc-dynamic-reconfigure: Support H265.	2022-12-01 09:45:24 +08:00
files	Move files from gst-plugins-bad into the "subprojects/gst-plugins-bad/" subdir	2021-09-24 16:14:36 -03:00
interactive	bad/soundtouch: Fix interactive test build on MSVC	2022-09-22 07:20:45 +00:00
validate	vtenc: apply DTS offset to ensure DTS <= PTS	2023-06-19 11:17:36 +01:00
meson.build	tests: rename 'icles' subdir to be more descriptive	2022-04-14 11:57:11 +00:00