07-13-2022 01:55 AM
Thank you for the response.
Unfortunately, it's not the memory or cpu (at least, ts/lv doesn't seem to be using much of either)
Also, I can skip ALL the main test steps and still have TS occasionally hang after the test is done with no cpu usage. Sometimes it hangs when I switch back after doing something else.
07-13-2022 02:44 AM - edited 07-13-2022 02:45 AM
Hi,
The TS hangs/slows down generally for either high CPU usage or Memory growth.
1) You can cross check with a simple sequence : Take a simple sequence which is a mixture of the steps that you are using in your test sequence. Ex LV steps.
Loop it so that the number of steps executed is much greater that those in your test sequence.
2) Try different loading/unloading options to free memory ( You can unload sub sequences once its gets executed and not wait till end of test)
Report options - Try to use OTF , Check offline processing unit option, Log only which is required ( Disable reporting forall unwanted steps),
Disable tracing
Check for any tight loops in the code modules that you are using ( loop with any delay)
3) Repair TestStand ( using Package Manager).
4) Disable few steps and sequence in your test sequence at a time and check which sub sequence or steps is resulting in this.
Please check if the above steps are useful in resolving your issue.
Ravi
07-13-2022 06:34 PM
+ 5) Check if you have any non-default search directories (Configure>>Search Directories...) that point to network drives, usb sticks, or other potentially unreliable or intermittent drives.
07-14-2022 12:02 PM
@James_Grey wrote:
+ 5) Check if you have any non-default search directories (Configure>>Search Directories...) that point to network drives, usb sticks, or other potentially unreliable or intermittent drives.
I will check, but I am certain that's not the case. But good thing to think about.
07-14-2022 12:06 PM
@RaviShrigiri wrote:
Hi,
The TS hangs/slows down generally for either high CPU usage or Memory growth.
1) You can cross check with a simple sequence : Take a simple sequence which is a mixture of the steps that you are using in your test sequence. Ex LV steps.
Loop it so that the number of steps executed is much greater that those in your test sequence.
2) Try different loading/unloading options to free memory ( You can unload sub sequences once its gets executed and not wait till end of test)
Report options - Try to use OTF , Check offline processing unit option, Log only which is required ( Disable reporting forall unwanted steps),
Disable tracing
Check for any tight loops in the code modules that you are using ( loop with any delay)
3) Repair TestStand ( using Package Manager).
4) Disable few steps and sequence in your test sequence at a time and check which sub sequence or steps is resulting in this.
Please check if the above steps are useful in resolving your issue.
Ravi
Problem is that it appears to happen randomly, even during edit. Like, I'll switch away and when I switch back TS will just grey out and hang for a long time. Processor is low. Memory is low. I think it's waiting for something, but that thing is not coming.
Def something I am doing though, because it follows me around when I pull code with git.
Next plan is to play and play without execution, to see if it's sequence editor, and not necessarily Execution.
07-14-2022 04:00 PM
I just had a situation in edit mode where I expanded FileGlobals and edited a value used in only one step in the currently displayed sequence. I changed that value and clicked out, and the editor hung for several minutes. No load on CPU, plenty of memory to go.
07-14-2022 04:44 PM - edited 07-14-2022 04:45 PM
Hi,
The next time the SeqEdit hangs can you create a dump file using the instructions below and share it with NI? You will have to use a third party location to host the dump file as it will likely be > 10 MB.
Open Windows' Task Manager, and can right-click the SeqEdit.exe process, then choose Create Dump File to create this dump file. If your are using and 64-bit operating system and 32-bit NI Software, you need to launch the 32-bit version of Task Manager, normally stored in the following location: C:\Windows\SysWOW64\taskmgr.exe"
Regards,
Anand Jain
NI