Non-Responsive LabVIEW Executable

[Troy12]

Hello,

I have an executable built in LabVIEW 8.6 that is deployed on target machines to run with the run-time engine (windows xp PC). The Application has a GUI with start and a stop button. I have noticed few instances of non-responsive GUI when the application is sitting idle. GUI is completely white and no buttons or menu options are visible on it at that time. 

I am not sure if something in the ini file is causing that issue. I have included the ini file that is created by LabVIEW when the executable is created.

Comments/suggestions are appreciated.

Thank you.

[jareds]

Hi Troy12,

I don't think any of the ini settings will cause an executable to become unresponsive.  Is your program doing anything when this happens?  If nothing is happening, you should check what other programs are running at this time.  It could be that another application is starving yours for a bit, preventing it from updating the GUI.  You should check the CPU usage when this occurs.

[Troy12]

Thank you, Jared.

No, my LabVIEW application is just sitting there idle (nothing running). I did look at CPU usage in task manager and did not notice anything out of the ordinary. My application however was listed as "Not Responding" in task manager. It is not happening consistently making it difficult to troubleshoot on target station. Hence I wanted to ask on the forum to determine root cause. Thanks! 

[Troy12]

I wanted to correct my last statement about CPU usage. The issue just happened again and I noticed the following in Task Manager > Processes:

CPU Usage: 0

MEM Usage: 367,188 K

The "X" button on the top right corner is greyed out in the actual executable, since there is a separate Exit button on the front panel, but when this issue happens, the "X" button is enabled (non responsive GUI image attached).

Comments are appreciated. Thanks.

[jareds]

You may want to see if this happens with all executables you build through LabVIEW or just this one.  I would build a very simple VI that waits for a user to close it and see if that behaves the same.  Also, how much memory do you have on your system?  What operating system are you using?

[Troy12]

Thanks again, Jared. I will give it a try.

The PC has 4 GB RAM and OS is windows XP.

[PJS]

Are you performing IO operations during the initialization?  Are you dynamically loading and DLLs/.Net assemblies during initialization?  I have seen what looks like a UI lockup on start only to find out that my system was having trouble with some IO at initialize (serial coms).  Also if you are dynamically loading DLLs, depending on what they do... they might be experiencing an issue.

[GregFreeman]

This may seem trivial but do you have any sort of "wait" in your loops? It could be as simple as starving the processor.