LabVIEW 8.5 crashes when I try to open this VI

[MSingh]

    A few days ago i was making changes to this VI for programmatically fitting the waveform graph to a pane on front panel. I was able to make some changes to the code successfully, saved the file and closed LabVIEW. But today i am not able to open the VI and LabVIEW crashes without giving any error codes.

There is too much work put into this main vi and it will take a long time to reproduce it. Please HELP!!!

[mikeporter]

Yup, it crashes. I would recommend that you go back to your last backup and work from there...

What's that? You don't have a recent backup? Hmmmm.... Consider this a lesson learned... Yet another good reason for source code control - daily backups.

Mike...

[Neil.Pate]

Crashes for me as well I am afraid,

But it is a pretty sad state of affairs that we have become so accustomed to corrupted VIs/projects. When was the last time you came across C code which brought down the IDE when loaded?

I have to say, 6.0, 7.0 and 7.1 (the other versions I have worked with), were far less prone to random shutdowns and corrupted code.

[MSingh]

Does NI have a way to salvage these corrupt VIs? There were only a few changes made towrds the end of the editing cycle and we should be able to discard those changes and retrieve the rest.

I hope someone says yes

[Pnt]

Maybe someone with Labview 8.6 beta can open it....

[mikeporter]

In general there is no way to recover a corrupt VI. Even if a later version can open it, that's no guarantee that it still isn't corrupt - just in a different way.

Mike...

[xntricity]

I've tried all the tricks I know of to recover this VI, but none of them have worked.

The only information I've managed to get from the crash is that it occurs in CopyAccumulator.cpp Line 36, suggest you pass this on to NI engineers and hopefully they'll be able to find a workaround for you. Other than that, you could try downloading the beta version of LV8.6 to see if that will open the file for you.

Regards,

Andy

[MSingh]

Hello Andy,

Thanks for the reply. I have not been able to get any error messages from windows. I am glad you could but am curious also how you got it. are you using a different debugger or some other program to extract this information?

Thanks again

MSingh

[MSingh]

Today I tried upgrading to ver 8.5.1 but had no luck. Same problem persists. I will be trying with 8.6 Beta version soon. I will keep you guys posted.

Thanks all for replying.

[Eriquito]

Hi MSingh,

I experienced the same problem when opening your VI in LabVIEW 8.5.1.

This was reported to R&D (#101847) for further investigation.

Unfortunately, Mr. Porter is correct in that usually there is no way to retrieve corrupt VIs; however, LabVIEW should simply give an error message rather than crashing.

Thanks for pointing this out.