[gstreamer-bugs] [Bug 584185] GstQueue NEWSEGMENT handling increases curtime even when queue is empty

[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=584185

  GStreamer | gstreamer (core) | Ver: 0.10.23




------- Comment #2 from Tommi Myöhänen  2009-05-29 08:48 UTC -------
Analysis of the log:

0:01:08.195709236: One buffer is added to queue. It is the only queue content.
0:01:08.197143563  NEWSEGMENT event is added to queue. It contains 2 items now.
...
0:01:08.206359872: Loop has taken the buffer and pushed it forward. Items = 1.
0:01:08.207580575: Loop starts handling the newsegment. Eventually  
update_time_level() is called, which contains following piece of code:

  if (sink_time >= src_time)
    queue->cur_level.time = sink_time - src_time;
  else
    queue->cur_level.time = 0;

This sets the cur_level.time to non-zero value and makes the queue look full,
even queue is now empty.

0:01:08.210968026: Loop waits for buffer. Note the changed queue duration!
0:01:08.235351571: New buffer arrives to queue
0:01:08.236206064: gst_queue_is_filled() returns TRUE
0:01:08.236938485: Queue tries to leak contents, but queue is empty


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