out of memory crashing on host

[JF-NRAO]

Hi all.  I have an application that I've been working with on and off for a long time for a research project.

I came back to it after leaving it sit for about 8 months, and now the software refuses to load  on the CRIO's realtime OS.

I have 2 VIs, one on the FPGA, and one on the realtime OS.  I can load the VI onto the FPGA, but when I go to load the VI on the realtime OS, the VI hangs after loading the last subvi, and the labview executable size on the host grows until it runs out of memory, whence it crashes. 

Any ideas on what might have happened to my windows host or my labview system to cause this?  I'm using labview 2010.  Nothing's been changed, to my knowledge, except maybe some windows updates.

Thanks for any ideas!

John

[Zachmx]

Are you seeing this problem when building a Real-Time Executable or on running an executable? If so, are you able to run a simple VI in interactive mode on the target from the LabVIEW Project?

[JF-NRAO]

I'm seeing it as the vi is downloaded to the crio for execution.  I will try another simpler VI.  One of my colleagues said that he saw this problem and updated his stuff to 2010 spi f4 and the problem went away, so I tried that.  No luck.  It still fails to load, and crashes the whole labview session.

John

[JF-NRAO]

OK.  I built a simple VI that just adds 2 numbers and displays them, and that downloads and works.  I guess that means that there's something in my code that's failing to work somehow.  There's a lot of interaction between the processor and the FPGA, but all of it has been working till now.

John

[Zachmx]

Have there been any version changes of the RIO driver or LabVIEW? Which RIO driver are you using and what model of cRIO is this happening on? You could be using all the memory on the controller.

[JF-NRAO]

Hi.  It turned out that my VI was somehow corrupted.  Today I reverted back a few versions of my user software and it works again.  Not sure what's wrong, but the system seems to work fine with an older code, so it must be something in my VI.  Thanks for the suggestions for isolating it.  I will just go forward from the version that works and get things going from there.

John