LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView crashes

  Dear Sir/Madam,

 

My program crashes every once in a while. The program acquires data from several phisical and simulated devices, processes it and pushes the result in circular buffers. When the buffer is full, the oldest elements are automatically deleted to give space for the new ones. These buffers are read, and the results are displayed, saved into a file, and send over internet with HTTP GET. On success, the respective elements are deleted from the respective buffers.

 

I have noticed that when the buffer is small (say, ~ 8000 entries), the program runs. I have not noticed it crash. However, when the buffers are larger (say, ~65000 entries), the program crashes soon after the buffer is full. What's interesting, a crash usually results in some of the loops dead but others still running. The DAQ and display loops are dead. The unimportant ones, i.e. the loop to display clock, and to read some data from the disk are alive.

 

The problem persists whether the program runs natively from LabView or is compiled with application builder.

 

I have attached the data saved by LabView to this messages.

 

Is there a way to identify what causes the crash? A technique or advice, perhaps?

 

Thanks!

 

Regards

Albert

0 Kudos
Message 1 of 6
(3,258 Views)

I can't look at your code right now (no downloading at work), but it sounds like the error happens when you cross 2^16 --> 65536...  So I am betting that one of your loop indices is tied to a U16 or maybe it can't exceed 2^16.  Can you identify which loop is causing you trouble?

 

-Matt Bradley

************ kudos always appreciated, but only when deserved **************************




Message 2 of 6
(3,232 Views)

  Dear Matt,

 

Thank you for the good guess. Unfortunately, it is not so. The last time I set the number to 65000. Also, Labview loops do not use u16 or i16. In addition, I do not use loops' counters, as the application is designed to work autonomosly over extended intervals of time.

The attachment is not the source code. It is the debug info for NI engineers.

 

Regards

Albert

Message Edited by alysko on 03-16-2009 05:10 PM
0 Kudos
Message 3 of 6
(3,222 Views)

Oh well... I'll try to get to it when I get home.  I'm not supposed to open attachments at work.

 

I thought for sure that had to be it.

 

 

-Matt Bradley

************ kudos always appreciated, but only when deserved **************************




0 Kudos
Message 4 of 6
(3,211 Views)

Hi Albert,

 

Is there an error message that pops up, or does LabVIEW just stop responding?  

 

Best Regards,

Bryan H.
0 Kudos
Message 5 of 6
(3,189 Views)

  Dear Bryan,

 

There is a error message. I will try to replicate the problem and will provide you with the message.

 

Some part of the program continues to work until I press OK button.

 

Regards

Albert

0 Kudos
Message 6 of 6
(3,174 Views)