[Bug]: restarting-writers causes SIGSEGV

[stephematician]

Is there an existing issue for this?

• I have searched the existing issues

Detail

Updated restarting-wrirers.sh due to outdated syntax:

@@ -15,7 +15,7 @@ run_writers() {
 }
 
 #v4l2-ctl -d $device -c keep_format=1 || exit 1
-./utils/v4l2loopback-ctl set-caps "video/x-raw, format=UYVY, width=640, height=480, framerate=(fraction)25/1" $device || exit 1
+./utils/v4l2loopback-ctl set-caps "$device" 'UYVY:640x480@25/1' || exit 1
 v4l2-ctl -d "$device" -c sustain_framerate=0 || exit 1

Then tried to run script:

user@home:~/v4l2loopback/$ sudo modprobe v4l2loopback /dev/video10
user@home:~/v4l2loopback/$ sudo ./examples/restarting-writer.sh /dev/video10
Using /dev/video10
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
Redistribute latency...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:00.040314196
Setting pipeline to NULL ...
Caught SIGSEGV

gst-launch version:

user@home:~/$ gst-launch-1.0 --version
gst-launch-1.0 version 1.24.2
GStreamer 1.24.2
https://launchpad.net/ubuntu/+source/gstreamer1.0

v4l2loopback version

v0.13.2-13-ge750af9

kernel version

Linux zephyrus-g15 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

OS Version

Ubuntu MATE 24.04 noble

Which CPU are you using?

amd64/x86_64 ("64bit Intel")

[stephematician]

Will be addressed with #611 (almost ready). Now shows test source, then a blank (green) screen every few seconds, then the test source again, and so on until finally the green screen.

I have also successfully set a timeout image that appears rather than the green screen - will put (required) changes to v4l2loopback-ctl in separate PR.