<html><head></head><body><div>On Wed, 2023-02-22 at 11:54 +0200, Mikael Nousiainen via gstreamer-devel wrote:</div><div><br></div><div>Hi Mikael,</div><div><br></div><div>1.18 is fairly old, it would be great if you could try a newer version such as 1.22.x.</div><div><br></div><div>One thing you could do after you noticed it stopped receiving packets is to attach a debugger such as gdb to gst-launch-1.0 via gdb -p `pidof gst-launch-1.0` and then get a stack trace of all threads to see where they're stuck and what they're waiting on.</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>There is no output from gst-launch-1.0 process when the UDP reception stops and I have not noticed any kernel messages at those times either. It is difficult for me to enable very verbose logging in gst-launch-1.0, as the issue might take weeks to show up and there's really no easy way to find space for the verbose logs.<br></div></blockquote><div><br></div><div>You could write a little application in C or python that creates a pipeline using gst_parse_launch() and starts it up.</div><div><br></div><div>With an application you can enable the ring buffer logger (gst_debug_add_ring_buffer_logger) to continuously log into memory.</div><div><br></div><div>You could then use a watchdog element in your pipeline to detect when data stops flowing, at which point you can then grab the last X MB or seconds of debug log from the ringbuffer and write it somewhere.</div><div><br></div><div>Cheers</div><div> Tim</div><div><span></span></div></body></html>