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
..
gst	d3d11bufferpool: Fix heavy CPU usage in case of fixed-size pool	2023-06-27 23:25:09 +00:00
meson.build