madgrizzle

If it helps, it failed today with a: >Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) ..and a just had another failure where it was landmarks_left stream....

Awesome, will try tonight! Thanks for looking into it.

It works great! Thanks for the fix!

Well, turns out that it just seems to work 'better', but it still crashes. I'm not entirely sure why I wasn't getting these messages before, but I recently did an...

Just curious.. is the "bug in depthai itself" a bug in the FW or a bug in depthai-python (or something else)?

I was hoping 2.11.0 would fix it for me (based upon what I saw in the commits and announcement), but I get the same error message (X_LINK_ERROR). I've seen @Luxonis-Brandon...

@themarpe, not immediately and the time it takes varies. At the moment, within 30 seconds or so. Couple days ago (I had built your develop branch hoping the fix was...

@themarpe, I spun up ubuntu 20.04 onto a RPI 4 and got everything installed and running with the same result after a few seconds. It did manage to spit out...

@themarpe I did some testing and got frustrating results. Not sure any of this is useful, but figured more information is better than none. I first incrementally enabled various parts...

@themarpe, you wrote: >"Regarding your observation - if you've removed that line, the actual on device processing should differ (the queue is non-blocking, the messages are going to continue being...