Memory management in *.exe versus *.so

[Michel_Gauvin]

Hello,

I have a LabVIEW application that must run as a daemon under Linux.  In order to eliminate the needs of the X display system, which is required by a normal LabVIEW .exe and prohibited by a daemon under Linux, I have followed the instructions located at http://digital.ni.com/public.nsf/allkb/5D6EC36DCF43343786257449006919E6 to create a *.so which is then called by a small .c application.  So far everything looks good and work.

My application must process hundreds and even thousands of files.  What I found out is that when used as a normal LabVIEW application the RAM is stable, but when used as a *.so the RAM gets to the sky (big memory leaks).  It is exactly the same source code that was used to built the LabVIEW application and the shared library.

- The c program that calls the *.so never return, in other words the *.so act as a standalone application.

- I'm using LabVIEW 2011 under Ubuntu 12.04 LTS.

Anyone has experienced this behavior?

Thanks,

Michel

[Michel_Gauvin]

Hello,

Ok, I made a few minor changes in the code and recompiled everything.  I looks like the memory leak is gone.... weird.

I will post again if I see it again and have a better understanding of what's going on.

Thanks,

Michel