In LabView 2010F2, when I am working on the Block Diagrams, if I do a Save or Save All or Clean Up Diagram, I frequently get a rotating circle and "not responding" mentioned in the title bar. Also sometimes I get this same behavior when I am in the midst of editing Block Diagrams. These events usually last from 3 to 15 seconds.
Today after a simple edit of a block diagram, I got the same "not responding" in the title bar, but this time it did not return from "not responding" even after more than 10 minutes of waiting. I had to eventually terminate LV 2010 using the Task Manager.
What would cause LV2010F2 to lock up and "not respond" for more than 10 minutes?
Why does LV show "not responding" at all ? I am using an Intel i5-750 CPU with 4GB RAM on Windows 7 Ultimate. It rarely shows more that 40% CPU usage and less than 1/2 RAM free, even during these "not responding" times. If LV 2010 is well designed internally, the Operating System should never show the application as "not responding". I do not see this problem with other WIndows applications, even Microsoft's Visual Studio 2010 when I have it doing heavy duty editing, building and debugging.
LV2010F2 should not hang up with "not responding" under any circumstance. If it is busy, it should show the hour glass icon. But it should always respond to the OS and accept UI input.
