memory graphs

[CyGa]

Hi!
In my application I have a VI in which I'm generating waveforms until the user presses a stop button. The data created is continuously displayed in a waveform chart.
I would have expected that the memory allocated to store and display data in the chart would be deallocated when the VI stops running. But obviously, looking at the Windows Task Manager it's not what's happening. I tried to force the data to be deallocated using these processes :

• write the chart property node "History" with an empty array
• write an empty array in the chart
• reinitialize the chart to its default value
• use the Deallocate Memory VI

None of these technics worked. Does somebody have an idea ?

[altenbach]

Could you attach the VI instead? It is almost impossible to troubleshoot an image.

1. What is your LabVIEW version?
2. What is the chart history size?
3. What is in the other cases?
4. You only have two sets of data, why are you branching it out to 8 sets?
5. The "stopAcq:disabled=0" property node belongs before the while loop. Once a control is enabled, it makes no sense to use an expensive property node to reenable it every 50ms, over and over again.
6. ...

[CyGa]

Dear Altenbach,

This VI is part of large project. I enclosed it to this message but you'll have to modify it a little bit to make it work.

To answer your questions :

1. My labVIEW version is 8.5
2. According to the task manager, before displaying data the amount of memory taken by labVIEW is 80 Mo. During signal generation, it climbs up to 140 Mo. So I'd say that thedata history size is 60 Mo.
3. In the other cases are other actions to perform. Basically, here are actions to quit (in that case I was trying to free the memory hold by the graph), and actions of initialization (controls placement on the front panel, etc...)
4. This VI will be used as a demo, so i just wanted to create the illusion that 8 signals can be displayed and controled without having to create 8 different signals. In a near future these signals will be replaced by data acquired using a FPGA acquisition card.
5. Yes you're right. It's just an error of inattention.
6. ...