Libnvargus_socket segfault

Hello,

We are trying to recover the stream of temporarily disconnected cameras in our application based on the libargus. When we detect a disconnection, we restart both producer and consumer to retrieve the stream. However, we sometimes face a segfault on libnvargus_socket.so.

  • How can we avoid/catch the segfault to avoid the application crash?
  • How to debug the libargus to understand where the segfault come from?

Here is the logs with gdb when the segfault is received: logs_gdb_segfault.txt (7.0 KB)

Here is the nvargus-daemon logs: logs_argus_daemon.txt (20.6 KB)

Our specs:

  • Jetson AGX Orin
  • Jetpack 5.1.3 / L4T 35.5.0

Thanks.

Please reference to the MMAPI sample like userAutoExposure10_argus_camera_recording to implement the error handle to terminal the APP to try.

We noticed that the segfault happens only on multiple camera streams. We tried to run the two samples simultaneously with 2 different cameras and we also have a segfault when a camera is disconnected (seems to come from the sample 10_argus_camera_recording).
Do you have a sample that handles errors for multiple camera streams ?

Current do not consider disconnect the camera.
Does your design able to detect camera disconnected?

We finally managed to retrieve the stream. However, we often face some argus errors on the disconnection which slow down a lot the recovery:

(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp,
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 137)
(Argus) Error Timeout:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)

Is there a way to avoid being blocked by these errors for a long time?

Replace the libnvscf.so by attached file
And run the argus_daemon by below command.

libnvscf.so.r35.5.inifite.txt (8.4 MB)

sudo service nvargus-daemon stop
sudo enableCamInfiniteTimeout=1 nvargus-daemon

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.