VI crash when trying to run - <process has already exited>

[BMathason]

I can not run or save my application without getting the message and LabVIEW crashing.

If I cause the VI to have a broken arrow, I can save the application without it crashing.

[Mads]

Is there anything in the code that might cause it? Code interface or call library nodes are typical suspects in this case. If not try copying the entire code to another VI and then save it. If that does not do the trick, could you upload the VI and it's subVIs as a library file here?

[Jeremy Braden]

In addition, you might also try pressing control-shift-run arrow to force a recompile of the binary executable of the VI. Most times you will not see anything happen but I have seen this technique solve a lot of problems.

Do you get the error if you run the VI on another computer?

[BMathason]

I don't have any code interfaces. I do have dll calls, but they have been in the application for years and I haven't had made any changes to that portion of the code. I've tried saving the vi to a new location, as a new developers build and the problem persists.

Unfortunately, the bug is in the main routine of a very large application that I can't upload.

[BMathason]

ctrl-shift-run arrow caused LabVIEW to crash with the same error. This sounds like a useful tip to remember for future problems.

I've tried running the VI on two Win2K machines. They crash, but I get a slightly different error message. One says " has generated errors and will be closed by Windows..." and the other says "LabVIEW.exe has generated errors and will be closed by Windows..."

[Mads]

I'm not talking about saving it as a new developer build - but making a new VI, selecting all the code in the old one and then just copy and paste into the empty one. This often fixes problems with insane objects. You are not getting any error messages mentioning insane objects so it might not be a solution...but worth a try though.

[BMathason]

I also tried copying all of the code in the block diagram to a new VI. This new VI also crashed when trying to save or compile.

[LarsRoe]

If you have a broken arrow, LabVIEW won't try to create runnable code for your VI. That could explain why it crashes only when it's runnable.

What version of LabVIEW and what OS are you using?

[BMathason]

It's LabVIEW 6.1 running on Win2K. I also tried it on WinNT and had the same problem.

[BMathason]

I suspect that this bug has to do with corruption of a property node...

I tried loading the application into LV7.0 (it was developed in 6.1). In LV6.1 it had a working run arrow, but in LV7.0 it came up with a broken arror. The error list included block diagram errors: "Property Node: invalid property". When I clicked on the show error button, LabVIEW crashed.

I've simply decided to go back to a version of the code before the problem and re-write the broken code. Thanks for the suggestions and tips. FYI, now that I have re-written the code in 6.1, it comes up in LV7.0 without a broken arrow as well.