labview 8.5.1 enormous bug

[DOC-doc]

Hi to all labview users and developpers,

I must report a very important bug that occured on my PC with Windows XP pro and Labview 8.5.1 :

After I changed the name of a global, some VIs using it have lost the link to the global item (as expected), but are still "runnable" and accept compilation.

When those VIs are called, they crash down labview.

Thank you for the time I lost trying to fix my bugs... 

For those who would not beleive me, please have a look at the screen copy.

[Intaris]

So you open the program using the globals and then rename the globals?

Sounds like a reference to a global doesn't actually load the global into memory unlike other types of VIs who are resident in memory whenever a program using them is loaded.

File a bug report.

Shane.

[DOC-doc]

Yes something like that.

How do you file a bug report?

[Mathan]

here

[Be sure if its a bug. If ur 100% confident, post it.]

Thanks,

Mathan

Message Edited by mathan on 06-26-2008 09:09 AM

[rpursley8]

I think I have seen something similar.  I changed a subvi's inputs and/or outputs and after relinking it on the block diagram I was working on, I got a clear run arrow.  When I ran it, LV 8.5.1 crashed.  Then opened the application back up it showed me other errors where that same subvi was used and it needed to be relinked.  Once I relinked each of those, it ran fine.

So for some reason, since I didn't have the other vis open that utilized this subvi, LV thought the app was compiled and ready to run when it really wasn't.  I will have to try to replicate this to have proof this is what happened.

[DOC-doc]

Now that you mentionned it, I also realize that I did recompile the VIs that same day

[AlexxxR]

Hi,

thats awesome. I saw your picture and I tried to reproduce this behaviour (in LabVIEW 8.5 and 8.5.1) but I´m not able. Can you please provide a small example or dedicated steps to reproduce?

Alexander Rudolph

NI Switzerland

AE Group Leader