Labview 8 crashes when saving a vi with a 'Bundle By Name' function

[cwalker]

We have a working vi (Get_AN_Fast.vi), created with Labview 7.1.

Trying to open this vi with Labview 8 crashes Labview.

Problem seems to be related to a 'Bundle by Name' function, but it is not that simple as using this function by itself wirks fine.

Any ideas would be a help.

[Wendy L]

Hello cwalker,

I was unable to reproduce the crash on my machine. Could you followup with additional instructions on how to reproduce it?  Thanks!

[cwalker]

To get it to crash on my machine, I just double-click on 'Get_AN_Fast.vi', Labview 8 launches, and I get the crash screen as shown in the attached picture.

My computer details are as follows:-

Processor - Intel Pentium 4, 3.2 GHz

Ram - 504 MBytes

Operating system - Windows XP Professional 2002, Service Pack 2,

Labview 7.1 and Labview 8 installed.

The vi opens fine with Labview 7.1, and we have had no problems opening and converting all of our other vi's with Labview 8.

The problem seems to be related to the 'Bundle By Name' function in the lower right hand corner because, if I disconnect one of the input elements, I can open and convert the vi usinf Labview 8 with no problem, but as soon as I reconnect the element and try and save the vi, I get the crash.

I have tried building a simple vi with just the 'Bundle by Name' function, and that works fine.

Charlie

[Wendy L]

Hello cwalker,

I'm still unable to reproduce the problem on my machine.  When that crash dialog appears again, I would suggest sending the error log to us here at National Instruments by clicking on the Send Error Report button.  This will further help us isolate the problem.

In the meantime, do have another machine with LabVIEW 8 on it?  Do you get the same behavior when you open your VI on that machine?  Which particular ActiveX Object are you connection to, because that is the only error I see when open your VI in LabVIEW 8 compared to LabVIEW 7.1?  You might also want to try repairing (Control Panel >> Add/Remove Programs) your installation of LabVIEW 8 to see if this helps the situation.

Thanks

[Ben]

mine does not crash but it opens broke.

What is the "IdaqIo" a reference to?

I probably do not have all of the componets loaded.

One more thing. Some of LV's type descriptors may have changed from 7.1 to 8.0.

Ben

Message Edited by Ben on 12-08-2005 08:07 PM

Message Edited by Ben on 12-08-2005 08:09 PM

[cwalker]

Sorry for the delay, I have been testing on other machines.

We can reproduce the error on other machines, with completly fresh installs of Labview 8.

The ActiveX Object we are connecting to is our own COM server, for interfacing to USB based data acquisition devices.

I have found that when our COM server is not installed on a computer, then the VI will open, but with errors related the the missing COM Server.

When the COM Server is installed, Labview 8 crashes when opening the vi.

I realise that our COM server might have bugs, but it worked fine with Labview 6 and 7, and it is Labview 8 that gives the error, not our COM Server (which is a stand-alone executable).

I have attached a zip file with our COM server, it just needs to be unzipped to a temporary file, and then run the 'register.bat' file to register the server.

It will not install any other files on your computer and, can just be deleted when you are finished.

Thanks

Charlie.

[Wendy L]

Hello Charlie,

I was able to reproduce the crash behavior with your COM server installed.  I also noticed, that if I take the ActiveX calls out of the main VI, the application will still crash in LabVIEW 8 with your server installed.  Having said that, were you able to trim down the code to the smallest set of VIs that are required in order to crash your application in LabVIEW 8.0 without doing so in LabVIEW 7.1?

Thanks.

[cwalker]

Wendy,

Its always a relief when someone else can replicate the problem, it means I wasn't being stupid.

I did try trimming down the vi to try and isolate the problem, and it seemed to be the 'Bundle By Name' function in the bottom right corner. If you disconnect one of the inputs, the vi is fine. However building a simple vi with with the 'Bundle By Name' function in the same configuration also worked OK, so the problem is not that simple. I will do some more trimming and try to narrow it down some more.

Charlie.

[cwalker]

Wendy, I have trimmed down the code a fair bit and it still crashes. Most importantly I have taken out all the references to our COM server, and it still crashes, even with our COM server unregistered.

All the references to out COM server resulted in arrays of varying dimension. I replaced these with hard coded arrays, and took out other bits of code as well.

Just open up the attached 'Get_AN_Fast_Trim1.vi' in Labview8, reattach the one broken link at the top (I have added a comment there), and save the vi.

Hopefully you will get the same crash as I do

Regards

Charlie.

[Ben]

Hi Charlie,

I can confirm your crash with the cod eyou posted.

I took the liberty of throwing away alot of the fluff and can still crash LV on demand now.

See image.

The LV code is attached.

I will let Wendy invoke the B word.

I think you have won a shiny new CAR.

Ben

Message Edited by Ben on 12-16-2005 06:43 PM