Labview crashes when saving after deleting property/invoke node

[MEastwood]

Hi,

I have a VI (attached) with four invoke/property nodes on, when I delete any one of them and try and save the VI, labview crashes. Im using Labview 8.5 but have also tried it on Labview 2009 with the same results. Can anybody else tell me why this is? Or can anyone delete these four nodes for me and let me know how youve done it?

Thanks,

Mark

[RavensFan]

Nope.  It crashes for me in LV 8.6.

I'm kind of suspicious of the "Interop dll" it is looking for while loading.  There is also a hidden control on the front panel that should be shown.

But try copying and pasting your block diagram from that VI into a fresh blank VI.  When I did that, I was able to delete those property nodes and save it.

[dhedges]

Hi Mark,

I just verified those four nodes are corrupt.  Sadly, the corruption doesn't do anything bad until you try to delete them.  Then it crashes when you try to save.

I went through and manually removed the corruption using LabVIEW 2009, and did a Save For Previous back to 8.5.  Hopefully, you can use the VI.

In the meantime, I would be very interested if you could give me a clue of how those nodes got corrupt.  It looks like they think they are .NET nodes, even though they're not.  Did you use copy or replace, perhaps?  Drag something from one VI to another?  Switch its class and undo?  I know it might be a shot in the dark, but if you can remember steps that can reproduce the corruption, we might be able to prevent this from happening to anybody else.

Thanks,

--Dan

[MEastwood]

They were originally .NET nodes, I then changed them only to try to delete them, I was using them originally with "Interop.DX10SDKADAPTORLib.dll" that the vi looks for when loading. The original .NET nodes wouldnt delete either, im not sure why, the reference to "Interop.DX10SDKADAPTORLib.dll" deleted fine.

Thanks

[dhedges]

I tried changing nodes from .NET to App just by right-clicking on them and going through the Select Class hierarchy, and I couldn't get the problem to happen.  But a colleague of mine says he thinks the problem happens when you try to load a .NET node where the .NET assembly is missing.  Apparently, that would cause the linkage to go bad, and later when you delete the node (whether or not you changed it to a different server class, it might not matter), then save, LabVIEW should crash.

Do you think that might have been what happened to this VI?

We're trying to verify this on our end.

Thanks,

--Dan

[MEastwood]

From the sounds of things, Id say thats exactly what happened, I deleted the .NET file before I tried deleting the nodes which would tie up with what your saying.

Thanks,

Mark

[muks]

Is this reported as a bug?

[Owen.S]

Hi muks,

Yes this has been reported:

 

CAR #178629

Thanks

[dhedges]

Thanks, Mark.  Corruptions like this one are tough.  Generally, we try to fix the original VI for the customer, and then add code to a future release that will detect the corruption.  On load, if we can fix the corruption we will, after reporting an error.  On save, if we detect a corruption we report it and fail the save.  But the trickiest and most important part is always to try to reproduce the corruption.  Thanks for your help!

--Dan