Simple Math VI crashes LabVIEW 2009 SP1

[counterzt]

Hi,

We previously filed a related issue, (ref #: 7302858). The last problem was resolved by 

Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.

However, the interesting crash happens again.

I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is

1. Add the "Word bits" as a connector on the diagram

2. Save it Then the VI begin to crash LabVIEW 2009 SP1.

Before the change, the VI was functioning all right.

Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?

Thanks,

Tian

[Joel Khan]

Tian,

Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it. 

I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted. 

<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE> 

[Darin.K]

Any recompile in LV9 caused a crash.  Adding to the connector pane is a red herring, any change triggering a recompile will suffice.

Create an indicator on the output of the upper shift register of the big For Loop (I64 array) and see if that puts a stop to it.

[counterzt]

Hi Joel,

Thanks for the recompile. However, it seems that it's recompiled in LV10, not LV9.0.1. My LV 9.0.1 cannot open it up. Would you mind to recompile it in LV9.0.1?

Much appreciated,

Tian

[counterzt]

Hi Darin,

It did stop the crashes! Any theory on what's causing this issue?  Why does the extra indicator trigger the recompile? What trigger the recompile?

Thanks,

Tian

[Darin.K]

Ours is not to wonder why... Glad it worked. Any non-cosmetic change will force a recompile when you next run or save. Another thing I would do is look at the code where you keep inserting an element at the beginning of the array. I would build the array normally and then reverse it at the end.