[Bug 737739] souphttpclientsink: Restarting after error results in buffers being queued forever
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Wed Oct 1 23:49:29 PDT 2014
https://bugzilla.gnome.org/show_bug.cgi?id=737739
GStreamer | gst-plugins-good | git
Sebastian Dröge (slomo) <slomo> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
Target Milestone|HEAD |1.5.1
--- Comment #2 from Sebastian Dröge (slomo) <slomo at coaxion.net> 2014-10-02 06:49:25 UTC ---
commit 374552a72093fa74e7d99f5a02219ce6674ff611
Author: Nirbheek Chauhan <nirbheek at centricular.com>
Date: Wed Oct 1 23:12:30 2014 +0530
souphttpclientsink: Add some more useful debug logging
commit 745d49731810d774463e72b03e759092e2b2e8b7
Author: Nirbheek Chauhan <nirbheek at centricular.com>
Date: Wed Oct 1 23:05:03 2014 +0530
souphttpclientsink: Free queued buffers in ::reset
::render sets a new callback for writing out new buffers only if there
aren't
already buffers queued for writing with a previously-scheduled callback.
However, if the previously-scheduled callback is interrupted by a state
change
(either manually or due to an error) and there are still buffers in the
queue,
restarting the pipeline will result in buffers being queued forever, and no
callbacks will ever be scheduled, and no buffers will be written out.
https://bugzilla.gnome.org/show_bug.cgi?id=737739
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list