[gstreamer-bugs] [Bug 523993] New: playbin2 blocks after a while when listening to a radio 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=523993

  GStreamer | gst-plugins-base | Ver: HEAD CVS
           Summary: playbin2 blocks after a while when listening to a radio
                    stream
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: sjoerd at luon.net
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


After listening to a internet radio stream for a while playbin2 blocks. Looking
into it with gdb revealed the following (only the relevant parts pasted):

Thread 4 (Thread 0x41001950 (LWP 27199)):
#0  0x00002b51aae3ed29 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
No symbol table info available.
#1  0x00002b51ae9a35a8 in gst_queue_chain (pad=<value optimized out>,
buffer=0x9261b0) at gstqueue2.c:1339
        started = 1
        queue = (GstQueue *) 0x76a020
        __PRETTY_FUNCTION__ = "gst_queue_chain"

Thread 5 (Thread 0x40800950 (LWP 27198)):
#0  0x00002b51aae3ed29 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
No symbol table info available.
#1  0x00002b51ae9a1d4a in gst_queue_loop (pad=<value optimized out>) at
gstqueue2.c:1509
        started = 1
        queue = (GstQueue *) 0x76a020
        ret = <value optimized out>
        __PRETTY_FUNCTION__ = "gst_queue_loop"



Looking into the gstqueue2 at the relevant lines showed that the waits are
respectively for removing/adding a queue.. So it's both waiting for an item to
be removed and to be added.. Using gdb to doublecheck:

(gdb) p ((GstQueue*) 0x76a020)->waiting_add
$48 = 1
(gdb) p ((GstQueue*) 0x76a020)->waiting_del
$49 = 1

Woopsie.. So let's see if it's actually empty:
(gdb) p ((GstQueue*) 0x76a020)->queue->length
$50 = 0

Apparently it is. So now let's see why it thinks it's full:

(gdb) p ((GstQueue*) 0x76a020)->max_level.buffers
$65 = 100
(gdb) p ((GstQueue*) 0x76a020)->cur_level.buffers
$66 = 0
(gdb) p ((GstQueue*) 0x76a020)->max_level.bytes
$67 = 2097152
(gdb) p ((GstQueue*) 0x76a020)->cur_level.bytes
$68 = 0
(gdb) p ((GstQueue*) 0x76a020)->max_level.time
$69 = 2000000000
(gdb) p ((GstQueue*) 0x76a020)->cur_level.time
$70 = 0
(gdb) p ((GstQueue*) 0x76a020)->use_rate_estimate 
$71 = 1
(gdb) p ((GstQueue*) 0x76a020)->max_level.rate_time
$72 = 2000000000
(gdb) p ((GstQueue*) 0x76a020)->cur_level.rate_time
$73 = 2015175107


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