LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV 2009 SP1 corrupts front panel VI during 'save' operation

My best guess is that corruption happens during 'save' operation.

Steps:

1. Slightly modify vi.

2. Run it, then stop and exit with saving of changes. (Saving takes unusual big amount time and cpu/memory resources)

3. Try to open vi and get the message "LabVIEW:Generic error... error code 3:Could not load front panel."

4. Exit from LabView

5. Start LabView and got the message "The last time you ran LabVIEW, an internal error or crash occurred at loaddata.cpp, line 3070"

 

Tried to reinstall LabView but it didn't help.

 

Any advice?

 

Thanks,

Boris

 

0 Kudos
Message 1 of 8
(3,330 Views)
Can you post the VI so we can see if we can duplicate the problem?
0 Kudos
Message 2 of 8
(3,324 Views)
Sure. Please see attached.
0 Kudos
Message 3 of 8
(3,321 Views)

Please post the un-corrupted version to see if the coruption is duplicated on other machine.

 

A corrupt VI is seldom useful since all it takes is a binary editor to corrupt a VI.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 8
(3,314 Views)

OK, Here it is.

Thanks.

0 Kudos
Message 5 of 8
(3,312 Views)

There were a lot of things that you did not post so I skipped through them.

 

Did a diagram clean-up and saved without issue.

 

maybe you should duplicate what I did (load with sub-VI and X-Controls adn save) to see if it is still corrupted for you. If not start adding stuff back in until you find what causing the crash.

 

So no crash on my machine.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 6 of 8
(3,303 Views)

Ok, I'll try to do what you've suggested.

Thanks a lot.

 

Boris

0 Kudos
Message 7 of 8
(3,294 Views)
It looks like rolling back to LabVIEW 8.6 solved the problem. Probably something bad happened during conversion of vi from 8.6 format to 9.0
0 Kudos
Message 8 of 8
(3,257 Views)