After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 796721 - queues: Should influence the number of allocated buffers when possible
queues: Should influence the number of allocated buffers when possible
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-06-29 14:34 UTC by Nicolas Dufresne (ndufresne)
Modified: 2018-11-03 12:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicolas Dufresne (ndufresne) 2018-06-29 14:34:49 UTC
As of now, queues completely ignore the allocation query. Though, for sized queue to work properly, you need enough buffers to be allocated. So far, most of the time this worked because the buffers pools can grow, or dynamic allocation is being used. In this bug report, I'm suggesting that queues, when they are configured with size in number of buffers, should influence the allocation query to ensure that they are useful and that their thread does not cause contention or starvation. Here's an example of starvation cause by queues (requires a driver that do not implement VIDIOC_CREATE_BUFS):

gst-launch-1.0 v4l2src device=/dev/video1 ! queue min-threshold-buffers=10 ! glimagesink sync=0

p.s. This case should also try and increase the latency, worked around using sync=0 here.
Comment 1 GStreamer system administrator 2018-11-03 12:47:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/300.