gstreamer/subprojects/gst-plugins-bad/tests/check
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
..
elements webrtcbin: Prevent critical warning when creating an additional data channel 2023-07-11 20:39:59 +00:00
generic Move files from gst-plugins-bad into the "subprojects/gst-plugins-bad/" subdir 2021-09-24 16:14:36 -03:00
libs d3d11bufferpool: Fix heavy CPU usage in case of fixed-size pool 2023-07-11 23:23:12 +00:00
media Move files from gst-plugins-bad into the "subprojects/gst-plugins-bad/" subdir 2021-09-24 16:14:36 -03:00
pipelines navigation: Add support for key Modifiers in all relevant events 2022-03-25 15:16:03 +00:00
gst-plugins-bad.supp Move files from gst-plugins-bad into the "subprojects/gst-plugins-bad/" subdir 2021-09-24 16:14:36 -03:00
meson.build d3d11bufferpool: Fix heavy CPU usage in case of fixed-size pool 2023-07-11 23:23:12 +00:00