@Alex-Kushleyev I can probably show you the backtrace log so that you can take a look at what causes the segfault.

@Alex-Kushleyev Thank you very much hopefully I can figure it out.

@Eric-Katzfey I reset all mpa services to factory settings and I keep getting the same segfault.

@Eric-Katzfey I would appreciate it if you could tell me what commands to use to stop all the services and then restart voxl-uvc-server or any resource that helps with debugging segfaults in general.

@Eric-Katzfey I don't know if it helps but whenever I run voxl-uvc-server, the segfault happens and after that the voxl-uvc-server service stops running, but is still enabled.

loading config file
Enabling debug messages

width: 640
height: 480
fps: 30
pipe_name: uvc

voxl-uvc-server starting
Image resolution 640x480, 30 fps chosen
Vendor ID 0x534d chosen
UVC initialized
Device 534d:0000 found
Device opened
uvc_get_stream_ctrl_format_size succeeded for format YUYV
Streaming starting

Segmentation fault:
Fault thread: voxl-uvc-server(tid: 16852)
Fault address: 0x7f7dda3000
Access to this address is not allowed.
Segmentation fault

@Eric-Katzfey so I stopped all services except for voxl-uvc-server:
Scanning services...

Service Name | Enabled | Running | CPU Usage

docker-autorun | Disabled | Not Running |
modallink-relink | Disabled | Not Running |
voxl-camera-server | Enabled | Not Running |
voxl-cpu-monitor | Enabled | Not Running |
voxl-dfs-server | Disabled | Not Running |
voxl-feature-tracker | Disabled | Not Running |
voxl-flow-server | Disabled | Not Running |
voxl-imu-server | Enabled | Not Running |
voxl-lepton-server | Disabled | Not Running |
voxl-mavcam-manager | Enabled | Not Running |
voxl-mavlink-server | Enabled | Not Running |
voxl-modem | Enabled | Not Running |
voxl-neopixel-manager | Disabled | Not Running |
voxl-open-vins-server | Disabled | Not Running |
voxl-portal | Enabled | Not Running |
voxl-px4-imu-server | Disabled | Not Running |
voxl-px4 | Enabled | Not Running |
voxl-qvio-server | Enabled | Not Running |
voxl-rangefinder-server | Disabled | Not Running |
voxl-remote-id | Disabled | Not Running |
voxl-softap | Disabled | Not Running |
voxl-static-ip | Disabled | Not Running |
voxl-streamer | Enabled | Not Running |
voxl-tag-detector | Disabled | Not Running |
voxl-tflite-server | Disabled | Not Running |
voxl-time-sync | Disabled | Not Running |
voxl-uvc-server | Enabled | Running | 0.0%
voxl-vision-hub | Enabled | Not Running |
voxl-wait-for-fs | Enabled | Completed |

And I am still getting the exact same segfault.

@Eric-Katzfey it seems that for some reason the voxl-uvc-server service just stops running by itself even after I run systemctl start voxl-uvc-server or systemctl enable voxl-uvc-server. Probably that causes the segfault, that the service is not running.

@Eric-Katzfey Thanks. Which services are the most likely to cause a segfault?

@Eric-Katzfey when I run voxl-uvc-server -f 15, 20, ... all lower frame rates give me the same seg fault. How can I stop other services from running?

@Róbert-Dévényi the SDK version is 1.2.0 and voxl-uvc-server version is 0.1.6.

I have bought the SIYI A8 mini gimbal camera and Sentinel perfectly detects it and I was able to stream video from it. Then, the next day something happened and since then I have been receiving this error: (the camera id is 534d, this is for certain)
voxl2:~$ voxl-uvc-server -v 534d -d
loading config file
Enabling debug messages

width: 640
height: 480
fps: 30
pipe_name: uvc

voxl-uvc-server starting
Image resolution 640x480, 30 fps chosen
Vendor ID 0x534d chosen
UVC initialized
Device 534d:0000 found
Device opened
uvc_get_stream_ctrl_format_size succeeded for format YUYV
Streaming starting

Segmentation fault:
Fault thread: voxl-uvc-server(tid: 17803)
Fault address: 0x7f9d661000
Access to this address is not allowed.
Segmentation fault

So it seems that the camera is recognized perfectly fine, streaming is started but then a segmentation fault occurs.
I would appreciate any help in this matter. I tried restarting the drone, the camera, killing the camera processing etc. hundreds of times, it seems that restarting / rebooting does not work
and this is some persistent problem.

Thanks for any help in advance.