11-25-2009 05:55 PM
Sometimes the Start Modal Dialog.vi gets stuck (i.e. won't return) and I cannot trace down because it asks for a password when I try and step into this sub vi. Needless to say the whole TestStand sequence is hosed at this point.
Is there something I can do to stop it from running indefinetely like this - and is the password available to step into it?
Thanks,
Ronnie
11-30-2009 04:48 PM - edited 11-30-2009 04:50 PM
Hello Ronnie,
You mentioned this happens intermittently. Can you identify any other behaviour that occurs when you see it get stuck? Can you provide more detail on how that particular vi is being used in the application and how it gets 'stuck'? Do you lose access to everything in Windows or in the UI? You are correct, since it is password protected you will not be able to step into the vi so we'll need to identify the inputs prior to this vi to identify the source of the issue.
11-30-2009 05:48 PM
Hello Glenn,
It does not return (i.e. gets 'stuck') after TestStand has been actively using that VI for some time.
I don't mean constantly like in a loop, but every now and again when that VI is called - and since it is part of the my Process Model it is a new Sequence Context every time.
The only way to resolve the situation is to exit TestStand and begin again.
Thanks,
Ronnie
12-01-2009 06:22 PM
12-07-2009 11:30 AM - edited 12-07-2009 11:34 AM
Glenn,
Sorry for the delay. Attached is the sequence file and the VI that has the problem.
The sequence file is a process model and it is the step in PreUUT of the "Test With Results" entry point.
The actual step is 'Get Model & Serial Info and Path' which calls "ESRT Get Model Serial Info and Path.vi".
I am wondering if it is a memory leak - because it only happens after a few hours (like this screenshot this morning).
I included the "ESRT SetForegroundWindow.vi" as it is part of getting the VI to be Modal in the "ESRT Get Model Serial Info and Path.vi".
I look forward to any comments you may have. Thanks,
Ronnie
12-08-2009 05:02 PM
Hi Ronnie,
Try disabling the following piece of code, and see if your application continues to hang.
I believe that what you are doing in your SetForeground.vi has already been handled by the Start Modal Dialog.vi
03-09-2011 01:15 AM
03-14-2011 09:31 AM
Did you follow the thread and see if that works from you? From the thread, it seems like the work being done in the Start Modal VI was being repeated in his code causing the error.