Labview crashes when it loads this VI

[sls__]

Hello! I am having trouble with a VI and I would like to know if someone can tell me how to proceed.

I am using LV 13.0f2. I was cleaning up one of my messiest VIs (NeuroF14). I compressed some code into a subVI, saved and kept on cleaning. Nothing happened yet. I was moving VIs and wires across the block diagram, when suddenly Labview crashed. It refused to recover the VI or open it.

After working all day on the issue and reading similar threads, here is what I found out:

- Labview crashes if I open NeuroF14 directly from windows explorer.

- It doesn't crash if I open a blank VI, insert NeuroF14 and open it from there. I can open the block diagram and change things. However, if then I try to save or run, it crashes.

The VI is part of a RT project. The project has one RT target to which NeuroF14 belongs. When using the project explorer:

- If I open NeuroF14 in the target, Labview crashes.

- No crash if I open it in "My computer". (A variable library is missing there)

- I I move the library to "My computer" too, and try to open the VI there, it crashes.

It's bizarre, and I can't find the origin of the problem. The one subVI I created (InitializeTarget.vi, the one on the left with the bulb) may be part of the issue. NeuroF13 is the version of the program just before I started cleaning up. Functionally, it's the same, but it works. NeuroF15 is the same as NeuroF14 but without the subvi. It also works. The funny thing is that I can open InitializeTarget.vi without trouble!

I'm attaching the project. It has the VIs and all dependencies.

I'd appreciate any input. Can you try to open NeuroF14? Thank you!

[JoLe]

Hi sls,

I opened your NeuroF14.vi in different LV versions. LV 2013 without patch / with f2 patch installed / on a Win 7 32-bit machine / on a Win 7 64-bit machine

and it showed always the same behaviour, similar to what you mentionned. This is what I discovered:

When I open your Bad.lvproj first, and open the NeuroF14.vi then out of the project explorer, it can be opened and LabVIEW does not crash.

When I open just the NeuroF14.vi directly from the Windows explorer by double clicking it, LabVIEW opens but while trying to open the VI, it crashes with an access violation error.

This looks like the VI was corrupted when you modified it.

Here is what I would try to fix this problem:

Create a new empty project and add all working VIs, subVIs, typedefs, etc. and save all files to a unused folder.
Open a blank VI and copy the blockdiagram of your bad VI to it. Save the VI in the folder of your new project and close it. Open the project file and then add the VI (unopened) to the project.

Then try to open the VI in both ways, see what is happening.

After you are copying the code of the corrupted VI, it is likely that this approach will fail.

When it is like that, in my opinion, there is no other option then creating the code again, symbol for symbol, wire for wire...

After there is a way to open the code of the corrupted VI, you can use it as programming reference, and therefore manually duplicate your code without too much effort.

Best Regards,

JoLe

National Instruments

Applications Engineering

www.ni.com/support

[sls__]

Hello JoLe, thanks for your reply and for reproducing the problem.

I have managed to control the VI. I don't know how I did it. I tried your approach until it crashed at some point, then tried a lot of different things (mostly making small rewires and saving), and after a while, the VI was stable again. I don't know if the corruption was "random" or if there is something to fix in LabVIEW. Perhaps someone can use this information and the code for fixing whatever went wrong!

Many thanks again!