[Bug 675010] After using queue2, souphttpsrc error-internal data flow error offen occurs

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=675010
  GStreamer | gst-plugins-good | unspecified

--- Comment #11 from yamin.sun.wz at renesas.com 2012-05-04 05:37:35 UTC ---
(In reply to comment #10)
> > so, would you like to answer my following questions:
> > 1. Is chunk size limited by gstsouphttpsrc?
> 
> Not sure I understand the question. Why would it be?
> 

Because the blocksize affects the error occurring rate seriously, so I guess if
 the blocksize has a range.



> > 2. At the beginning of running gst-launch, memory is enough, why  'failed to
> > allocate 10485760 bytes' is reported?
> 
> Because at the beginning your 20MB large queue2 is empty. After a while it
> fills up, so at some point (if it ever gets that far) there's 20MB less space
> available than there was when gst-launch started, without any memory leaks
> involved.
> 
> You may also be interested in bug #664778, which could be related.


  I have read the content in bug #664778 and understood it mostly. 
  In fact at first, I also found the same problem with memory waste(I think it
is memory leak, because I do not know intrinsic factor), and found the
relationship between blocksize and memory waste:
  the larger the blocksize is, the less the memory waste is.

  So I use larger blocksize, but 'internal data flow error' occurs.
  Now, in the final analysis, it is the memory waste breeding the error.

  So I also want to modify gst_soup_http_src_chunk_allocator myself, but I am 
newcomer to gstreamer and solving the problem is an urgent thing for me. 

  Could you like to give me some advices?  


> It's still not clear to me there's actually a bug in souphttpsrc here (other
> than the one mentioned above).

  Is still there a bug in souphttpsrc?
  Could I learn about the 'bug'?
  thanks.

-- 
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.