[gstreamer-bugs] [Bug 540300] [souphttpsrc] souphttpsrc does not seek ahead in http stream

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=540300

  GStreamer | gst-plugins-good | Ver: HEAD CVS




------- Comment #15 from Wouter Cloetens  2008-08-02 00:46 UTC -------
Created an attachment (id=115712)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=115712&action=view)
Fix behaviour when seeking extremly rapidly and fix libsoup assert.

Cool, somebody wrote a seek test program. The seek test was pretty broken when
I wrote souphttpsrc.
I understand the behaviour now. The case is indeed caused by timing; a new seek
that cancels the HTTP request before connection setup is complete will cause
it. The seek program exhibits that nasty behaviour by triggering seeks while
dragging the position scroll bar.
The patch in attachment 115643 probably covers all cases. I'm attaching a patch
that exposes this case more visibly through a new 'cancelled' state, active
only when the connection is being torn down, which actually only happens as a
result of a seek.
The seek program also triggers an assert by libsoup in some cases, that the
SoupMessage we use is not a valid SoupMessage. This is caused by attempting to
cancel a SoupMessage whose lifecycle had already ended, so it's a bug. Removing
our pointer to it in gst_soup_http_src_response_cb() fixes that.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=540300.