frankshieh
According to my checks, atleast the stereo_depth_video raises a "Communication Exception" which usually indicates FW (device side) crash/brownout (either a bug or power consumption issue)
I suggest that you power your device (I presume OAK-D) with the provided 5V power supply along the USB connection as inadequate power supply capabilities by USB only is usually the cause for this exception to be raised.
(More interpretation of the issue ahead)
As for the exception and interpretation of it, I highly suspect that above screenshots don't point to IO exception as I've suggested before, but this is only where the programs execution was at the moment when an exception was raised (and was left unhandled, which made the program crash), which makes sense as a lot of time is spent waiting in that cv::waitKey function compared to the rest of the loop.
To verify this, do modify an example and add a try/catch statement around the main loop which catches and prints the raised exception:
try {
... // main example loop
catch (const std::runtime_error& ex){
std::cout << ex.what()
}
