Aaron -
The trace messages are from the TestStand engine and they suggest that a type is not being released and the type is still in a type usage list. Typically this occurs because a sequence file is not being released properly, i.e. calling ReleaseSequenceFile and then releasing the object. Sequence files have a type usage list attached to them and the usage list is also added to an internal global list in the engine.
You need to isolate what object is not being released properly. First do the trace messages show up if you just open and close your GUI? Do you have to call the Login front-end callback to have the trace messages show up? Do you have to open and close a sequence, do you have to run the sequence for the trace messages to show up?
Sc
ott Richardson (NI)
Scott Richardson
https://testeract.com