Error message that no virtual memory pops up & crashes when application is run for more than 1 hour

Question

My application uses VISA serial operations. It has arrays to store data collected from various devices. I reinitialise the arrays each time the index reaches 50.
Data acquisitions is carried out in separate threads by invoking the runVI method.
When i run the application on Win XP continuaously for more than 1 hour it gives an error message that no more virtual memory to complete the task and the system hangs up.
I open the serial port only once and close it when the application is terminated. But serial read/write operations are done continuaously
Is the error caused due to memory leakage? How can i solve the problem. It's very urgent and i shall be thankful if i ge
t the help.

Answer 1

Yes, it sounds like a memory leakage (either that or you're trying to run an advanced app on an old computer w/ little memory and a small hard drive).
Things to try:
1. Ensure it's only labview, and not say labview and another application interacting. This isn't a likely case, but you never know what people have on their boxes and I've seen some weird things with virus scanners. Hit Ctrl-Shift-Esc to get the task manager. Go to processes and watch the memory consumption (click Memory twice to sort in descending order) of the various processes. If labview keeps rising, you've got a leak.
2. If only a reasonable amount of memory is being used, double check your page file settings (read virtual memory).
From the Control Panel
Select System
Select
Advanced Tab
Under Performance, select the Settings button
Select Advanced Tab
Under Virtual Memory, let windows dynamically adjust the page file (and any XP speed tweakers out there can now chime in about how wrong this is. This essentially allows windows to keep upping the virtual memory as needed by various processes.
3. Find the leak. In LV Tools->Advanced->Profile VIs. Turn on memory stats. Start the profiler. Start your vi. If the vi crashes labview totally, you'll have to keep hitting snapshot to find the leaky vi (the one that's memory keeps growing).
4. Upload the vi to the forum so we can give it a looksee.
G'luck
2006 Ultimate LabVIEW G-eek.