[gstreamer-bugs] [Bug 584185] New: 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
           Summary: GstQueue NEWSEGMENT handling increases curtime even when
                    queue is empty
           Product: GStreamer
           Version: 0.10.23
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: ext-tommi.myohanen at nokia.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
In camerabin there is a queue which leads from videobin to viewfinder. In my
setup this queue max-size-buffers is set to 1, and it is leaky downstream. I
managed to get the following situation to happen:

1. in gst_queue_loop(): gst_queue_locked_dequeue() receives a NEWSEGMENT event,
which is the only item in the queue.
2. Handling the event causes apply_segment() function to be called, which in
turn calls update_time_level().
3. Now queue->cur_level.time is set to non-zero, even when the queue is empty.
In my case the value is quite big (bigger than max-size-time).
4. Next time when chain function is called, gst_queue_is_filled() thinks that
queue is full and starts leaking it (downstream in my case, but this doesn't
matter actually).
5. Trying to leak empty queue causes assertion failure:

ERROR:gstqueue.c:858:gst_queue_leak_downstream: assertion failed: (leak !=
NULL)

This happens when camerabin's video recording is switched to pause and back to
recording multiple times in a row. Eventually this problem will show up. 

Attached is a log that shows what happens. I have added one debug line ("queue
is full, leaking buffer on downstream end") myself to see that it really starts
the leaking operation.


Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:


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