Hi anireno,
this behaviour sounds strange. We have LabVIEW with NIDAQmx and VISA running on flash systems with really small resources running stable for days and weeks.
There are, however, known but undocumented memory leaks in LabVIEW.
I had the same problem with a leak in one of my apps that killed my system afer 3 days.
Here the problem was a waveform chart. Using waveform charts fills up your memory, no matter how big the "history length" is. This is a NI-known fact on EVERY OS (Windows, Linux, Solaris,...) since August 2006 but it has not been fixed yet. (I think I will open an angy thread about publishing known bugs and using bugzilla...).
In general Via Eden/C3 should work fine. We have been using those for a while but switched to a more rugged and long-time-available board some time ago.
Can you give me a little bit more information on your system? Are you running Madriva 2006 on your VIA-Board? Do you have hardware drivers as wenn (VISA, NIDAQmx,...) or just the plain LabVIEW Runtime Engine?
Are you sure LV is eating the memory?
Have you tried to trace the memory usage? You probably know how to do that, eg using pmap -x <PID>.
I usually write the memory usage to file every minute or so (sleep 60). In bash this could look like this (replace myapp with the name of your app):
while (( 1 )); do pmap -x $(ps aux|grep myapp|grep -v grep|awk '{print $2}')|grep 'total kB'>>memlog.txt;sleep 60;done
( this command: $(ps aux|grep myapp|grep -v grep|awk '{print $2}') just fetches the process ID for you.)
I hope this helps a little bit.
If you are interested in a gentoo-based 70MB flash-OS let me know. The system we use should run on some VIA-boards (but not all. Problem is VIA changes chipsets like underwear and you never know what you get when you by a new one. There are even differences between EDEN and EDEN-processors. And on a small flashdisk-OS you just can't support every network driver in the world)
We have LV8.0 and NIDAQmx, a VNC server, samba, ftp, ssh, scp, busybox integrated.
The reason we didn't publish it is that you have to have a little bit linux background to install it (eg grub-configuration) and the documentation is not really brilliant. And the LV-RTE is not GNU anyways (why?? who knows)
so long
-DB