Win10 C++ demo ucrtbase.dll exceptions!

@frankshieh what does the exception message say?
You can try catching the exception using a try/catch statement and printing the what() message. Windows doesn't usually print these out nicely.

You may also try building the example as Debug to get a more informative stack trace.

frankshieh If you can compile in Debug configuration and try capturing the exception again, you can upload the dump file somewhere and send me the link - I'll give it a try and analyze to see why it came to this state.

Check the following documentation for VS: https://docs.microsoft.com/en-us/visualstudio/debugger/using-dump-files?view=vs-2019#BKMK_Create_a_dump_file

Also include the needed files (OpenCV dll, pdb & exe for the application you are debugging) as per: https://docs.microsoft.com/en-us/visualstudio/debugger/using-dump-files?view=vs-2019#BKMK_Find_binariessymbol_pdbfilesand_source_files

frankshieh Thanks - will let you know how it goes.

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()
}

frankshieh
I don't see the python3.9.dmp in the onedrive folder - can you recheck?

How does Linux stability compare to Windows?

We are working hard to make sure our platform is stable across all platforms. I'll dive deeper into this issue.

I understand you require stability in your case - I'd still suggest properly doing exception handling to cover for any exceptional events. On that note, you may also automatically recover if an Communication Exception is raised, by reconnecting to the device and continuing the execution of the pipeline. This of course depends on you use case if couple of seconds (3-4s) of downtime are permitted.

Regarding power consumption, this is an area we haven't strongly optimized for yet. We do aim of reducing this after we have the base feature set covered.

frankshieh
Thanks for this information - I'll look if the high fps could be the culprit here