09-15-2007 09:30 AM
09-15-2007 11:44 AM
09-17-2007 08:17 AM
09-17-2007 08:27 AM
09-17-2007 09:37 AM
09-17-2007 11:35 AM
09-17-2007 11:38 AM
09-17-2007 11:49 AM
I have no tools to analyze these problems from the provided data.
Have you tried to just look at the memory use via task manager every couple of hours (before it crashes!) and see if it increases over time.
For example, if you are building infinite arrays in shift registers or constantly create references without ever closing them, "request deallocation" won't help you at all. It cannot deallocate what you still have in use.
Please show us your LabVIEW code instead so we can point out potential problem areas.
09-17-2007 05:45 PM
09-18-2007 10:43 AM
If the points are equally spaced in time, maybe you want to use plain scalar data on your chart instead of waveforms and set x0 and dx once at the beginning. I could imagine that all these timestamps would create much more overhead for the code.
I never use it that way, so I am not sure what it does internally.
Do you really need to update the chart via a property node? This also causes more overhead.