[gstreamer-bugs] [Bug 611042] New: [adder] many pads, 'sink has no event handler'

[GStreamer (bugzilla.gnome.org)]

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

           Summary: [adder] many pads, 'sink has no event handler'
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.25
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: prince.buster at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Using a Python script that dynamically plugs new bins into a single adder,
without leaving the PLAYING state. 

It does this indefinitely, swapping in new bins whenever the old ones expire
(i.e, reach EOS). The result is a continuous, layered stream of sound, from
various file sources.

Each time a new bin is linked to the adder, a request pad is obtained, with
name sink%d. The integer %d increases rapidly as the program runs; many bins
are added and removed.

When %d reaches anywhere above 100 (has gotten upto 600 before), I eventually
get this error:

(slurry.py:3365): GStreamer-WARNING **: pad adder:sink115 has no event handler,
file a bug.

So here I am, filing a bug.

I suspect the problem could be avoided by re-using previous request pads
instead of getting new ones. They are being released, but not reused.
Regardless, there shouldn't be upper limits!

If any more information is required, I am happy to oblige.

x
Jez

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