To gsflat -
You appear to have created a global variable called "m_oExecution" which I assume that you have created using
CA_DuplicateObjHandle() within some callback. If you are just copying a callback parameter to your global variable, the handle may have already been released.
If you fail to call CA_DiscardObjHandle() on object handles that you duplicate before shutdown or before you reassign a new value to an already assigned variable, TestStand will not be able to release the object on shutdown and you will get these debug warnings. Failing to properly release any type of object handle can result in these warnings.
As to why you release build is erroring, you will have to determine which functions in the project that uses the tsErrChkMsgPopup
macro are failing and then figure out why.
Scott Richardson (NI)
Scott Richardson
https://testeract.com