Hello,
I am working with LV 8.5, Win XP. My application has about 700 vi's. When I run it as a development system or as an EXE, the same problem occurs. The page file that XP uses starts at 400MB and continues to grow until it almost reaches 2GB and then crashes. The performance degraded long before them. I am running a number of serial devices that also have data that is gathered and sent to an MS SQL 2005 Database. The more devices active, the fater the page file fills up. With 10 devices, the it takes about 2wk to get to 1.5GB. With 100 devices it takes about 1 day.
I can narrow the problem down to logging of the data, since if I do not log, the memory does not increase. However, this is still a large area with many interactive vi's. I havve looked for the obvious things as explained in the knowledge base like unbounded array's etc. I have also used the profiling and buffering tools in LabVIEW and cannot find the problem.
The page file does not return to normal unless I exit from LabVIEW completely. Closing the VIs does not free up the memory. It is as if LabVIEW uses some memory, decides it is not a big enough block, then allocates a new contiguous block without freeing up the old block.
Is there a better set of diagnostic tools I can use to pinpoint the memory leak? How can I find the problem?
Thanks
Ron
