More sw crashes after upgrading to V5.0.6

Software C++
1

I have updated the sdk to V5.0.6 and recompiled or own software on a Orin AGX Dev kit with v1.3.1 stereolabs duo capture card.

Then I notice that the sw crashes after some minutes with the following error:

terminate called after throwing an instance of ‘std::future_error’
what(): std::future_error: No associated state
Aborted (core dumped)

I didn’t change anything in my sw, so it seems related to the latest V5.0.6 release.

any ideas how to fix this?

2

Hi @Martijn
Thank you for reporting this issue.

Do you have a snippet of code to replicate the problem and eventually fix it?

3

I let it run in gdb and got the following bt:

(gdb) bt
#0  \__pthread_kill_implementation (threadid=281474468079680, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x0000fffff44bf244 in \__pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x0000fffff447a67c in \__GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3  0x0000fffff4467130 in \__GI_abort () at ./stdlib/abort.c:79
#4  0x0000fffff47653d0 in \__gnu_cxx::\__verbose_terminate_handler() () at /lib/aarch64-linux-gnu/libstdc++.so.6
#5  0x0000fffff4762b4c in  () at /lib/aarch64-linux-gnu/libstdc++.so.6
#6  0x0000fffff4762bb0 in  () at /lib/aarch64-linux-gnu/libstdc++.so.6
#7  0x0000fffff4762e94 in  () at /lib/aarch64-linux-gnu/libstdc++.so.6
#8  0x0000fffff475e594 in std::\__throw_future_error(int) () at /lib/aarch64-linux-gnu/libstdc++.so.6
#9  0x0000fffff6bb5c40 in sl::CameraMemberHandler::run_corrupted_frame_detector() () at /usr/local/zed/lib/libsl_zed.so
#10 0x0000fffff6bb5ed4 in sl::CameraMemberHandler::quality_check_work() () at /usr/local/zed/lib/libsl_zed.so
#11 0x0000fffff47929cc in  () at /lib/aarch64-linux-gnu/libstdc++.so.6
#12 0x0000fffff44bd5b8 in start_thread (arg=0x0) at ./nptl/pthread_create.c:442
#13 0x0000fffff4525edc in thread_start () at ../sysdeps/unix/sysv/linux/aarch64/clone.S:79
4

Hi @Martijn
The SDK team is analyzing the problem to replicate and fix it.
A code snippet that allows for easily replicating the issue would be useful to speed up the process.

5

A fix will be released with v5.0.7 soon.