[Bug 699794] New: Network played stream leaks thread after end-of-stream reached

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=699794
  GStreamer | gst-plugins-base | 1.0.6

           Summary: Network played stream leaks thread after end-of-stream
                    reached
    Classification: Platform
           Product: GStreamer
           Version: 1.0.6
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: henner.zeller+gnomebugzilla at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=243449)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=243449)
Test program to reproduce.

Affects 1.0 but as well seen in 0.10

With each stream played over the network (here: sounds via HTTP), a thread is
leaked. Probably some thread created for streaming/buffering that never is
cleaned up after the stream has stopped playing.

In the attached example, I play a URL over and over; whenever end of stream is
reached (in bus message GST_MESSAGE_EOS), the URL is re-played via a

  GST_STATE_READY, set-uri, GST_STATE_PLAYING

sequence.

With standard Linux tools, we can see that the number of threads increase by
one for every repetition played, without ever getting cleaned up:

while : ; do ps -eLf | grep ./test-loop | grep -v grep | wc -l ; sleep 1 ; done

Eventually, this ties up so many threads, that things stop working
(as happening for the project I am working on that uses gstreamer:
gmrender-resurrect )

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