labview crashes when I create an override method

[Timmar]

I get this message when I new>>vi for Override>>[select ancestor]>>ok .. File Save

At first it only happened with one override method but it appears to have spread over time and will crash on 10 or so ancestor VI's now.

The fault is a little like this one, I haven't actively removed the front panel from my vi's but abview crashes so often it is not unusual for the occasional VI to be corrupted so, anything is possible.

[Sergey_Kolbunov]

This kind of crash reports does not give you enough information on what is actually going on. I can only agree that it may be some corrupted files in an ancestor chain. The slow but effective method to fix potentially corrupted files is to create new vi and copy block diagram from corrupted vi to the new one. We did that procedure successfully couple times to recover crashing code.

[Timmar]

How do I know which vi's are corrupted?

in the last few days I have vi's that just won't open.

I have been deleting them from the class and either re-creating them or rolling them back from source control.

My project has 2,741 vi's it is a bit of a needle in a haystack exercise

[Timmar]

Sergey,

I have given you a Kudos,

I created a new project and moved my code across, I can create override methods again and it doesn't crash quite as much.

I can't accept this as a solution, I still don't understand how currupted VI's and Labview Crashes can me my fault.

I am not hacking them with an xml editor or anything like that, I am just using labview to create and modify them...

If they are corrupted I expect the compiler to tell me.

[Sergey_Kolbunov]

Timmar,

I'm glad to hear that my advise helped you. This is a real pain if something like you describes helped with project or vis and hard to figure out why that happened and what is actually wrong with them. This is not a solution but some kind of symptomatic treatment, you do your "rain dance" around computer and it may help 🙂

[Timmar]

Sergey,

I have recently done some coding Metrics,

I spend more than 75% of my Debug time performing a Labview "Rain Dance".  I am not Bragging mind you, I write some pretty buggy code, but I perform detailed tests and resolve them quite quickly.