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 530637 - queue leak on capacity change
queue leak on capacity change
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.19
Other All
: Normal normal
: 0.10.20
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-29 22:25 UTC by Jonas Holmberg
Modified: 2008-04-30 09:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
queue patch (3.48 KB, patch)
2008-04-29 22:28 UTC, Jonas Holmberg 		committed Details | Review

Description Jonas Holmberg 2008-04-29 22:25:12 UTC 
Please describe the problem:
When a max capacity property (max-size-*) is decreased on a downstream leaky queue , it does not unref buffers until a new buffer is pushed on its sink pad, even though it could handle downstream leak immediately.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Jonas Holmberg 2008-04-29 22:28:21 UTC 
Created attachment 110133 [details] [review]
queue patch
Comment 2 Wim Taymans 2008-04-30 09:36:12 UTC 
        Patch by: Jonas Holmberg <jonas dot holmberg at axis dot com>

        * plugins/elements/gstqueue.c: (gst_queue_leak_downstream),
        (gst_queue_chain), (queue_capacity_change),
        (gst_queue_set_property):
        When changing thr max capacity of a leaky queue, immediatly drop buffers
        instead of waiting for a push on the sinkpad. Fixes #530637.