gsignal.c:2641: instance has no handler with id

[Krutskikh Ivan]

It turns out that the glitch is on multisocketsink and I can only
observe this with more that 3 clients connected to gstreamer pipeline.
Switching to tcpserversink didn't make any difference. So the bug is
somewhere in those elements

пн, 15 июл. 2019 г. в 18:05, Krutskikh Ivan <stein.hak at gmail.com>:
>
> Hi everyone.
>
> I'm in some bad situation right here. My application uses gstreamer
> pipelines with multisocketsink for video distribution to remote
> clients. It's written in python and distributes video from rtspsrc of
> ip cams. Each pipeline run in separate process so no intersection is
> possible there. At first everything is fine and works as expected, but
> after some time log starts spamming:
>
> июл 15 16:18:26 archive videoserver.py[30994]: sys:1: Warning:
> ../../../../gobject/gsignal.c:2641: instance '0x7f39cc046870' has no
> handler with id '943'
> июл 15 16:18:27 archive videoserver.py[30994]: sys:1: Warning:
> ../../../../gobject/gsignal.c:2641: instance '0x7f39b40e9d90' has no
> handler with id '1072'
> июл 15 16:18:30 archive videoserver.py[30994]: sys:1: Warning:
> ../../../../gobject/gsignal.c:2641: instance '0x7f39b4107130' has no
> handler with id '6641'
> июл 15 16:18:34 archive videoserver.py[30994]: sys:1: Warning:
> ../../../../gobject/gsignal.c:2641: instance '0x7f39c002e880' has no
> handler with id '2505'
> июл 15 16:18:44 archive videoserver.py[30994]: sys:1: Warning:
> ../../../../gobject/gsignal.c:2641: instance '0x7f3998102b40' has no
> handler with id '3013'
>
> And so on. Each warning results in process crush and data loss. The
> only signals that I'm using are 'client-added',
> 'client-socket-removed' for multisocketsink and 'split-now' for
> splitmuxsink on recording needs.
>
> What can I do to solve this behavior ?