Open Petrox opened 2 years ago
I am getting this same error on one of my production boxes using OAK-D-POE using standard center RGB camera. For whatever reason that one box throws it after ~10-90 minutes of running continuously. However, another box I upgraded using the same hardware (PC & cameras) has been running solid for 3 days on the 2.15.0 release.
Stack trace (most recent call last):
Sorry for the issues at hand @Petrox @chris-piekarski
@Petrox how long after the segfault arrises on the example you've ran? Is it immediate or happens after some time of running? Also can you share the low quality disparity images and in what scenario were they taken? (CC: @Erol444 on disparity images) EDIT: I think those should be available here: https://github.com/luxonis/depthai-python/issues/521
@chris-piekarski Were both boxes running version 2.15.0? If that is the case, do you happen to know any other differences that might be at play here.
In any case, we are still on the hunt to track down some additional stability issues, which I think could be pertinent here in both cases. We'll keep you updated
Yes both boxes running 2.15.0 @themarpe One that doesn't fail: using mono 720p with only crop manip at 15 fps NN One that fails: using RGB with manip crop and rotate at 30 fps NN
We'll take a further look into this and get back
Computer: corei7-7700hq with lots of ram and IO, no resource starving.
The disparity image was low quality, displayed "ghosts" (non existent close objects which were visible when I moved the camera (oak-d-lite), then suddenly segfault. (which is not an acceptable way to handle any issues)