LabView freezes when I try to open a VI

[RobertMai]

Hello everybody,

I guess I finally made it to get another VI corrupted... again.

The case is as follows:

I have a VI that works quite fine - I can open it, run it, edit it and save it. And by saving it the problem begins: The next time I try to open it, Labview freezes and produces about 90% load to one of my CPU cores - I can only kill it through Task Manager. So the VI seems to be corrupted...


Why does this happen (so often!)?

How can I rescue my still-working-but-no-more-if-being-changed VI? (Copy&Paste to a new one makes all frontpanel elements get invisible - and since someone from NI telephone support told me that Copy&Paste shouldn't be used at all (btw: ?!?) - this method doesn't seem to get me off the problem)

Why are there no possibilities to repair corrupted VIs? There must be some way to do this. I can't imagine that NI made up a data format that can't be restored at all - not even partially - when one tiny byte or something else goes to nirwana. Or did this VI-Format really grow this large that no one knows what's going on in there any more?


I know there are many topics on corrupted VIs here... and on most of them the answer is: "There's nothing that can be done. Use a backup or write a new VI."
Since my VI that works and does not work anymore after saving actually is my backup, rewriting it will cost a lot of time and problems like this keep coming up on my projects again and again (not only on my projects but also on those of colleagues developing with LabView) I couldn't resist to post this topic...

[RobertMai]

p.S.: I'm using LV 8.0.1

[Kodeeswaran]

Do you get any error messages like insane object error, couple of times i also had that problem and then i recoded it, its because of cut copy and paste only, and also when your code is too lenghthy and the variables scattered you might get this proble, does your PC configuration has enough memory to handle the LabVIEW program increase your RAM and check it out..

[altenbach]

Do you remember what kind of edits you did? What does the VI do? Is it simple? Very complex?

Is it possible that your VI contains a huge calculation to be folded into a constant. Have you tried just to wait a bit longer when opening it?

Do you mind posting the VI here, maybe we can e.g. try to open in in 8.2.1 for example to see if it makes a difference.

Message Edited by altenbach on 08-03-2007 07:53 AM

[RobertMai]

Hi,

now that I've returned from my vacation I tried some other things...

At first: thanks for your answers. The VI is quite complex... using several ActiveX-functions to control 3rd party software.The computer I am working on should have enough memory to handle this VI.

I tried to first save my VI (the one i can still open) as a LV 7.1 VI. After that I reopened it and since then I can also open it again after I changed the VI (what caused LV to freeze before). I hope that it's still doing its work although...

Greetings!

Robert

[mikeporter]

What is on the front panel of the VI that you are openning? Also what antivirus software are you using? There is a known problem with accessing the MAX database that can cause very long (in the order of several minute) delays when opening VIs with resource name controls on their front panels. There was even a knowledgebase article on it - which I can't seem to locate right now.

Mike...