Labview 2011 FDS (64bit) crashes when saving a vi with MATLAB node

[rolfk]

---

@Amd1480 wrote:

did anybody could solve or got a work arround this problem?

I am getting the same error code when I use the Call Library Function to call external DLLs in my application.

I am using the following system configuration:

- Windows 7 32bit with SP1

- LabVIEW PDS 2011 32bit

Additionally to this error I am getting the following message (Ausnahme: Access violation (0xC0000005) bei EIP=0x00C0503F) (see attachments)

Note: calling the same DLLs using previous LabVIEW versions (8.2) works fine.

---

When such errors happen in an application that uses the Call Library Node, you can be almost certain that it is a problem in how the Call Library Node was configured (wrong!) or a bug in the DLL. That you happen to see this error, only means that the external code happend to overwrite memory that it was not supposed to do, and that memory happened to be some data structure that LabVIEW uses to represent some front panel element. That it didn't happen in 8.2 doesn't mean that it didn't have that error there too, only that it overwrote some different memory location, that had unluckily for you no visible consequences.

For all other cases with no Call Library Node included, it means that the VIs front panel resource got somehow damaged (and yes this could also happen from running the VI in an application with misbehaving Call Library Node, and then saving the VI). The most easy solution is to rewrite the VI, another option is to try to force a recompile with the Ctrl button pressed and then activating the run button in the VI toolbar. Other than that there is little we normal users can do. The only people who can do more here are the LabVIEW developers who can look inside the VI and identify the damaged data structure and repair it, but that is a lot of work and time, and NI doesn't commit to doing this normally.

[Wintermute2]

I believe I have something to contribute to this thread.  I pipe data from a Matlab script to another Matlab script and I found that when I have the data cofigured into a very long 1D complex array I get the error when I attempt to save my VI however when I change the data type to 2D complex matrix I no longer error out.  Hope this helps.

[dyanna]

That actually worked for me. Idk why i need to convert my 1D array into 2D array and convert back to 1D, but the labview stopped crashing after that modification.

[Hfactory]

Same here with LV2012 on Windows 8.1 64bit. After reading Wintermute2's solution, I converted all arrays connected to the Matlab script node from 1-d arrays to 2-d arrays and the problem disappeared.