I wrote a small test program using normal Queue calls then ran it both on my development platform and on a 8176 realtime processor to compare the behavior:
ObtainQueue ForLoop N times EnqueueElement QueueStatus EndForLoop ReleaseQueue The program worked normally on the development platform and I could not exhaust memory (virtual memory available). Then I ran it on the 256 megabyte RAM realtime processor and when I set the loop trip N high enough, the program acted abnormally. I got about 216 megabytes on queue before failure. On the console display of the realtime processor I could see a message line "Not enough memory to complete this operation", but the ErrorStatus outputs from all of the queue VIs showed "no error". The only symptom of abnormal program operation was the front panel showed program stopped (visual appearance of run-arrow and abort button) short of the requested number of iterations. My question: Why was "no error" reported from the EnqueueElement ErrorStatus output and the error was posted to the console display screen of the RTP?