We are developing a Smart Client 2018 R2 plugin based on the MediaRGBVideoEnhancementLive example. Occasionally, the Smart Client pops up an error dialog with an AccessViolationException and a call stack indicating that the problem is occurring in our plugin. However, the call stack ends at the entry point to our C++ code, so it’s hard to determine where exactly this is happening. We do have debug symbols enabled in the build of the suspect C++ code.
We have been able to reproduce the error while the Visual Studio 2015 debugger is attached to the Smart Client process, but it seems like the Smart Client may be handling the exception before it would cause the debugger to stop the program. In this case, we still didn’t get a useful call stack.
Any advice would be appreciated.
You use Smart Client 2018R2, which MIP SDK version do you use? (2018R3, 2018R2 or older version?)
The MIP SDK version is also 2018 R2.
We had a know issue to the SDK and the Smart Client RGB Video Enhancement
sample but fixed in 2018R2, so this was my reason for asking.
Do you know whether using the unmodified sample will cause the same exception?
Sorry, we do not really have a good idea how to get to the issue when the debugging fails like you describe.
!. We have a Smart Client RGB Video Enhancement sample yet you mention the Media RGB Enhancement Live standalone sample. My first assumption has been that you must be using the Smart Client sample but maybe there is something here. Please look into the Smart Client sample if not already doing so..
We never encountered this problem with the unmodified sample, so it’s most certainly some problem in our C++ code, but the lack of detailed call stack is making it difficult to track down. Do you know if there is a way to stop the Smart Client from handling the exception and just let the program dump core at the point our code makes the access violation?
Regarding which sample we started from, you’re right – I think it was not MediaRGBVideoEnhancementLive, but rather “PluginSamples/RGBVideoEnhancement”.
There is no such Smart Client functionality.
I wonder if you will get closer if you setup Visual Studio to “break when thrown” on the exception. (You might already.)
Yes, we did have “break when thrown” enabled for the exception, but somehow the debugger still didn’t catch it. Thanks for looking into it anyway.