LabView 2010F2 Not Responding

[SimpleeLaura]

---

Jon S. wrote:

I wanted to commented on one thing that Ben had mentioned.  We do not expect any certain part of LabVIEW to be prone to crash.  In cases where LabVIEW is crashing and we have identified the problem we have made adjustments to our code to either fix the problem or handle it gracefully.  We do take crashes very seriously and want to get as much information as possible. LabVIEW R&D is working with Don to try and figure out the cause of his behavior.  When we identify what is wrong we will take action to correct the problem.

SimpleeLaura: Do you have code that will reproduce this behavior?  Can you share it with us?  If you don't feel comfortable posting your code on a public forum you can create a service request if you have a valid service contract.  If not please contact our customer support (1-800-531-5066) and tell them that you need to report a bug.

Ben's workaround will proabably be beneficial to use.  You can use block diagram cleanup on smaller sections of code instead of the entire application.  In the applications that I have worked on I rarely use my main VI because the way in which you organize higher level VIs is usually different than how a smaller subVI that only handles a certain task is laid out.  The clean up tool works the best of VIs that fit our style guidelines

---

Thanks, Jon. I will look into a service request. 

[Andrey_Dmitriev]

---

@Jon S. wrote:

 We do not expect any certain part of LabVIEW to be prone to crash.  In cases where LabVIEW is crashing and we have identified the problem we have made adjustments to our code to either fix the problem or handle it gracefully.  We do take crashes very seriously and want to get as much information as possible. LabVIEW R&D is working with Don to try and figure out the cause of his behavior.  When we identify what is wrong we will take action to correct the problem...

---

Hi, Jon,

Fully understand that public forum is not "bug report tool", but anyway look how version 2010 works (crashes collected for last month):

During building of Project:

(very informative)

During editing: Ctrl+Z was pressed multiple times:

During closing project with XControl:

(well, it seems to be trouble in MSVC run time)

During renaming library in project:

(happened multiple times)

During Mass Compile:

(its not crash, but very informative - which object caused this???)

During deleting broken wires:

(happened multiple times)

Most of this crashes happened sporadically, so, I can't send bug report. Two weeks ago upgraded with latest 10f2, but situation is not better. Just today was crashed two times.

Andrey.

[Jon_S.]

Hello Everyone,

I have a little bit more information for all of you regarding LabVIEW windows being tagged "Not Responding".

Windows 7 has lowered its threshold for when it will label a window as Not Responding.  If you want a little bit more info on this you can look at the first paragraph of this MSDN article.  Basically in a window is unresponsive to user interaction (e.g. mouse clicks) for 5 seconds, Windows will ghost the window and display "Not Responding" in the title bar.  When a window is ghosted all that the user can do is move, resize or close the window.

Many operations in LabVIEW need to run in the UI thread because running them in parallel could cause severe consequences.  For example, changing a block diagram while trying to compile could cause problems for LabVIEW.  Drawing is another operation that runs in the UI thread.  This is why large block diagrams can show this behavior when cleanup is run on them.

One way to avoid the annoying Not Responding ghost window is to not try to interact with the window while it is doing one of these operations.

We have recognized that because Windows 7 is more liberal at assigning this flag to our windows that we need to try to prevent this from happening.  Because of this we have filed CAR 256141 to investigate possible solutions.  This CAR has been added to the LabVIEW 2010 Known Issues list.

Thanks!

[Jeremy_Marquis]

I found this thread investigating my own "hang" behavior, which occurs often when opening VI's and also seemingly at random while editing them, and also every time I try to do a deployment to a hardware target.  Several coworkers have the same problem.

After reading here, I was wondering if this had to do with the autosave feature in the Environment options.  Does that feature get called whenever you open a VI?

Jeremy

[PaulRB]

Hi Jeremy,

I don't believe that the autosave feature compiles the code, so it should not be causing this hang. The actual save process could be causing it, but I have never seen that before. 

Is there anything else you are doing when this occurs? What version of LabVIEW is it?

[Jeremy_Marquis]

LabVIEW 10.0 (2010).  It seems to happen much more often when I open VI's that are targeted to a RT PXI controller.  I have several projects targeting different RT PXI controllers and they all do this.  There are several of my coworkers that are having the same problem on thier computers with the same version of LabVIEW.

So, different projects, different hardware targets, different computers, all showing this behavior.  Same LabVIEW version, all using LV RT, all targeting RT PXI platforms (haven't tried it with cRIO/cFP).

Thanks.

[MegaHertz]

Hi Jeremy,

As mentioned above by Jon S., R&D is currently looking into this issue. If this is causing a critical issue for you, please contact NI Support and mention this forum post. Thanks.

[Clint_Eastwood1000]

Hey Andy,

Did the "not reponding" issue ever get resolved??  I was wondering if it goes away when you create an exe out of Labview files??

Thanks..

[Blizzard]

Hello Clint,

R&D is still looking into this issue. The current workaround is to wait until the task is finished before you try to interact with the window. We don't have any documentation about the issue going away when creating and exe out of LabVIEW files. As mentioned before, if this is causing a critical issue for you, please contact NI Support and mention this forum post.

Have a happy Holiday,

Anna L

[Clint_Eastwood1000]

Thanks..  I'll wait until I create the exe to see if it affects anything.  It hasn't anything other than annoying for now..