GNOME Bugzilla – Bug 596404
file descriptor leak
Last modified: 2009-10-29 21:45:06 UTC
if in a piece of python code you do something like self.multisink.emit('remove',host,port) where self.multisink is a multiudpsink element, the file descriptor are never released and so there is a file descriptor leak
Not a bug. As the documentation explains: "In all cases, multifdsink will never close a file descriptor itself. The user of multifdsink is responsible for closing all file descriptors. This can for example be done in response to the #GstMultiFdSink::client-fd-removed signal." You need to close the fd when you're done with it.
Sorry Michael, but I'm using multiudpsink not multifdsink and multiudpsink have no property to close fd, even if multiudpsink is related in some way to multifdsink at least is needed some more documentation, thanks Nicola
Oops - sorry, I misread your original bug report. For multiudpsink you need to listen to the client-removed signal (which should be emitted after you call remove), and close the FD yourself there. This is still not a bug, but my pointer was to the wrong documentation - sorry.
sorry Michael, I know this is a bug tracker and not and help system but client-removed return host and port not fd. http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-multiudpsink.html#GstMultiUDPSink-client-removed In multiudpsink the only thing related to fd is the property closefd and according to the documentation is true for defaults, so or this is a bug or there is something undocumented, thanks Nicola
Sorry my mistake the fd leak wasn't caused by gstreamer, Nicola