02-24-2017 08:25 AM - edited 02-24-2017 08:29 AM
I wanted to have an VI that automatically updates VI prototypes in a Test Stand sequence. The program does that, but also gives me some error messages:
References to PropertyObjects were not released properly. Total number of objects: 6010 Number of top-level objects: 35 Note: Some top-level objects may be included if they are referenced by an incorrectly released top-level object. For example, an unreleased SequenceContext object references a SequenceFile object. The following top-level objects were not released: Type Definitions [35 object(s) not released] Type Definition #1: Name: MessagePopup etc
But I tried my best to delete all the references that I got...
Did I miss something?
Solved! Go to Solution.
02-24-2017 09:13 AM
Oh my, is this any better?
02-24-2017 04:00 PM
You shouldn't need the call to Engine.ShutDown since you're using the Application Manager. ApplicationMgr.Shutdown will release the Engine for you.
Hope this helps!
Trent
02-27-2017 01:07 AM - edited 02-27-2017 01:22 AM
It seems to work better now. I've never thought that too many stops and shutdowns can be a problem ;).
But on the other hand I've started seeing errors like:
Exception: Access violation (0xC0000005) at EIP=0x00000000309F9CA0
Version: 14.0.1 (64-bit)
The error comes from this VI (I guess) - this VI is part of the post-build process after packing an lvlibp; I'm still trying to debug it somehow.
02-27-2017 02:50 AM
The said exception/access violation happens somewhere inside the inner case. where the Modules are loaded or the modules are forced to reload prototypes. Why?
Is it a problem with the access to the file from which I want to reload the prototypes (an lvlibp)? It could make sense, as this VI is run from the post build action of the said packed library...
03-01-2017 07:43 AM
Have you had a look at these?
How Can I Update All The VI Calls In A TestStand Sequence?
http://digital.ni.com/public.nsf/allkb/D7CB87B8EE52E7978625758400762D2D
Reload Module Prototypes Programmatically with a TestStand Sequence
03-01-2017 08:02 AM
@.aCe. wrote:
Have you had a look at these?
How Can I Update All The VI Calls In A TestStand Sequence?
http://digital.ni.com/public.nsf/allkb/D7CB87B8EE52E7978625758400762D2D
Reload Module Prototypes Programmatically with a TestStand Sequence
http://www.ni.com/example/30267/en/
Yes, and this is not what I was searching for.
03-01-2017 10:41 AM
@nikodem wrote:
@.aCe. wrote:
Have you had a look at these?
How Can I Update All The VI Calls In A TestStand Sequence?
http://digital.ni.com/public.nsf/allkb/D7CB87B8EE52E7978625758400762D2D
Reload Module Prototypes Programmatically with a TestStand Sequence
http://www.ni.com/example/30267/en/
Yes, and this is not what I was searching for.
I get that, the example sequence is doing exactly what you are doing but in teststand. The example uses flags for open sequence, module.load etc evaluate if they are relevant to you.
03-02-2017 12:48 AM
Actually I just did that, and managed to get it to work (generally) using TS.methods, but I ran into issues with some Access Violations, as stated above. More details about this problem is to be found here - http://forums.ni.com/t5/LabVIEW/Exception-Access-violation-0xC0000005-at-EIP-0x00000000309F9CA0/td-p...