BUG: LabVIEW 8.6 crashes when you save a class vi with the same name

[Matthew_Kelton]

I am running into an annoying crash.  If you try to add a VI with the same name to an existing class, LabVIEW will notify you that you made an error.  Once you hit OK, LabVIEW crashes.  Obviously, the workaround is not to save any VI with the same name as an existing VI to your class.

[LaRisa_M]

Hi Matthew,

First, thanks for taking the time to report the crash on the forum. I wanted to check if your crash was reproducible, but I couldn't get LabVIEW to crash for me. I created a project in LabVIEW 8.6, created a LabVIEW class, and added two VI's to the class. When I tried to name the second VI the same as the first, LabVIEW asks first if I want to replace the existing VI. If I select "Yes" the error message says "Cannot save VI. Another VI in memory is already loaded from that path." and it takes me back to the save menu. No crash. Did you do anything differently, do you have anything else in your project, or are you using an OS other than Windows XP? When you start LabVIEW again after the crash, does it alert you that an error occured last time LabVIEW was run? Do you have an option to report the error? If so, I suggest reporting it. That sends the crash data to us by email, and it really helps us troubleshoot the crash.

[Matthew_Kelton]

I have attached a ZIP file with an example project.  Open the project and open one of the VIs in Test Class.  Choose File->Save As.  Choose Copy->Open additional copy.  Make sure the box for Add copy to Test Class.lvclass is checked.

Do NOT try to save the VI over top of the existing VI.   Go to a new folder and save the VI without changing the name.  LabVIEW will save the VI, then inidcate it cannot add the file due to a naming conflict.  Once you hit OK, LabVIEW may or may not hang for a few seconds, then crash.

When LabVIEW restarts, it does not indicate anything happened. It just comes up with the standard startup screen.

I stumbled across this attempting to create a copy of an existing VI, but forgetting to change the name.

I confirmed this does not happen in LabVIEW 8.5.1, so the behavior is new to 8.6.

Message Edited by Matthew Kelton on 12-19-2008 07:52 AM

[LaRisa_M]

Hi Matthew,

I found a Bug Report for a crash like this occuring on Vista machines when you try to save a VI with the same name in any type of LabVIEW class. It looks like it's isolated to Vista, and I didn't get a crash following your steps on Windows XP. The good news is that R&D has already finished programming better save instructions and warnings that will prevent users from being able to save the VI in this way and avoid the crash. That fix is all ready for the next 8.6 revision, but I don't have any information on when that will be released. I'm adding your steps to the report, so R&D can be sure they didn't miss anything. Thanks again for letting us know how you ran into this. It definitely helps us make LabVIEW better and better.

[Matthew_Kelton]

LaRisa,

I am using XP with the latest service packs, so it is not just Vista.

Matthew

[LaRisa_M]

Hi Matthew,

I tried reproducing this again since you mentioned you were using XP, and now after 2 days of not crashing, it is crashing consistently on my Windows XP machine. Weird, and valuable. It's also giving me an error that points to functions at the C++ level, which isn't what the Vista issue was caused by. So, it's a new bug report. We'll need to develop a better way of handling the error. Thanks again for all your great information. When I get this all documented for R&D, I'll let you know what the Corrective Action Request ID number is, so you can track the issue's status in future releases, if you want.

Have a happy holiday!

[Bhatia]

I am facing the same problem.

The concept of LVclass where you have a vi for override in a child class  - the vi has to be of the same name.

My project works ok in version 8.5.1 but not in version 8.6.

Can LaRisa advise how to get the version of LV8.6 with this bug fixed ?

Very urgent !

Regards

[LaRisa_M]

The Corrective Action Request which I filed for this bug is ID #138429.

Bhatia, currently there is not a fix. It is in the works. You should not run into the problem if you are overriding the vi. If you try to save the vi to another location and do not override the first, then the error will occur. What more specifically is your project doing when it saves the vi with the same name? I may be able to make a better suggestion for you.

[Bhatia]

Thank you Lisa for your response.

My Project uses LVClasses about 100 of them in the project.

In a parent class there is a vi with dynamic terminals.  In a child class when I create a vi for override, the name of the vi has to be the same as in the parent class.  I am getting into problem when I try to save the VI.

The essence of OOPs is that the name of the VI is the same ( Just refer to camera example in OOPs) in several classes.

If I save the VI with a different name, the purpose and power of OOPs will be lost.

My project works ok in version 8.5.1 but crashes in 8.6 version. 

It is important for me to use version 8.6 because I use several large statecharts.  Performance of statecharts has greatly improved in version 8.6.  In 8.5 and 8.5.1 the statechart crashes very often and time to compile is more than 10 minutes on a quad core machine with 4 GB ram and running vista.

I really need support to get over this problem.

Regards

[Matthew_Kelton]

Is LabVIEW crashing when you save the VI or when you run your program?  I have no issues creating an override VI, as that VI is in a different class.  My issue is unintentionally trying to save a VI of the same name into the same class.  You get the error message that a VI of the same name exists, then LabVIEW crashes.  What exactly happens when you try to save your override VI?