RT Code aborts

Question

Hi
We have been facing a strange problem for over 2 weeks.
We have developed an application that works on client-server communication.
PXI-RT acts as the server and the RT application is delpoyed to run on startup.
Host PC receives data continuously from the RT for analysis, processing and display.
the RT acquries data from a max of 63 channels (PXI and SCXI), decimates the data by a factor defined by the user and transmits it to the host.
for over few days, the RT code was observed to abort execution after nearly 20 min of execution. Data was acquried from a max of 63 channels at 5KS/sec.The RT aborted irrespective of the number of channels being configured for acquisiton.
The duration after which the code aborts varies between 10 min and 20 min.
We were not able to trace the reason for this behaviour. We tried increasing the delays and timeouts in the communication vis.
If anyone out there can suggest the possible fixes to this issue, it would be grateful.
Any more information regardign the system, if needed, will be given.
Thank you 

Answer 1

MScap wrote:
Memory does not change rapidly. It increases slowly to around 60% before the code aborts. The CPU usage jumps between a higher and a lower value, till it actually ends up either at 0% or at 100% 
Message Edited by MScap on 11-10-2008 08:53 PM
If memory is growing even slowly to 60%, I would strongly suspect a memory leak.  Does anything about what you are doing in the code make sense that the memory is growing?
I would suspect that you have arrays that are growing with time.  If the array grows to be larger than the space it currently occupies, then the memory manager will shuffle it in memory until if finds a contiguous space in memory to hold it.  If the array grows so large that there isn't a large enough block of memory to hold it, then I believe the system would crash.  Even though you are only using 60%, that means only 40% is free, thus less than half the memory.  If the array has grown over time, the array may now be larger than 40% of your memory space.
Take a close look at what operations you are doing to your arrays and make sure you are not growing them unnecessarily.  Preallocate space for arrays by using initialize array functions.  Use replace array subset in code rather than build array or insert into array, maintaining the array between loop iterations using shift registers along with any other data you need to hold such as how much of the array contains valid data.