Seungha Yang b18bd5ec2b 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/4935>		2023-06-27 23:25:09 +00:00
..
check	d3d11bufferpool: Fix heavy CPU usage in case of fixed-size pool	2023-06-27 23:25:09 +00:00
examples	qt6d3d11: Add Direct3D11 Qt6 QML sink	2023-06-21 15:32:17 +00: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	streamcollection: Use upstream-id as name	2023-06-22 14:06:04 +02:00
meson.build	gstreamer-full: add full static support	2023-05-31 15:17:11 +00:00