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 763801 - queue2: typo in out rate calculation
queue2: typo in out rate calculation
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other All
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 758891 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-03-17 10:27 UTC by Chandra Prakash
Modified: 2017-11-23 17:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
queue2: fixed typo in out rate calculation (1.22 KB, patch)
2016-03-17 10:29 UTC, Chandra Prakash
rejected Details | Review

Description Chandra Prakash 2016-03-17 10:27:17 UTC
In my platform I was facing below 2 issues while plying 4K mkv stream using http
 1. queue2 is consuming more and more memory.
 2. while running, I encounter frequent pauses due to buffering

While investigation I found that in gstqueue2.c/update_out_rate() byte_in_rate was used instead of byte_out_rate.

On correcting this typo, above 2 issue are resolved.

Thanks,
Chandra
Comment 1 Chandra Prakash 2016-03-17 10:29:32 UTC
Created attachment 324162 [details] [review]
queue2: fixed typo in out rate calculation
Comment 2 Sebastian Dröge (slomo) 2016-03-17 11:57:02 UTC
Thanks for your patch. It seems like this code is intentionally like it is though, as discussed on IRC:

  <wtay> the level in the queue is based on the input rate
  <wtay> not ever the output rate
  <wtay> the output rate is there for the query only

Can you check why and where queue2 is consuming more and more memory for you? Where the memory piles up? Does your queue2 have any of the max-* properties set to 0? Are you running it in ringbuffer mode, temp-template mode, or use-buffering mode?
Comment 3 Chandra Prakash 2016-03-21 05:00:27 UTC
Thanks for quick reply. 

My queue2 have one non-zero max-* property and rest are set to 0
  max-size-buffer=0
  max-size-bytes=0
  max-size-time=500000000
  use-buffering=TRUE
I am investigating at my side why this patch is resolving my scenario?
Can you please inform me if above queue2 properties are ok?
Comment 4 Sebastian Dröge (slomo) 2016-03-21 07:01:28 UTC
Does your input to the queue2 have correct timestamps?
Comment 5 Tim-Philipp Müller 2016-05-15 07:02:19 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!
Comment 6 Edward Hervey 2017-11-23 17:12:13 UTC
*** Bug 758891 has been marked as a duplicate of this bug. ***