clear arrays pragmatically

[Arroyo]

Thanks for that tip.

But my main question is how to dispose the inputs arrays just after these have been converted to images?

[Arroyo]

Thanks for that tip.

My main question, however, is how to dispose the input arrays once they have been converted into images?

Regards

[Gregory]

I think you just wait for the subVI to finish executing.

[Arroyo]

Mmmm...That does not seem to work.

When I open my program, LabVIEW consumes about 150MB.

Once I have executed, LabVIEW consumes 1,2 GB. 

All the arrays that were created as inputs of the different subVIs are stored. I would like to dispose them to solve this issue. 

[Gregory]

Are the subVI's front panels open when you run your program, or just the main VI?

[Arroyo]

Just the main one. 

The problem was so bad at some point that I had to change the static calling of the SubVIs for dynamic.

Still, I have some issues with memory.  

[Eric1977]

You're not doing somethilg silly like loading the image and then making that a local variable every time to each SubVI, are you?

[Kyle97330]

Can you try putting the Request Deallocation Function on your SubVI with a True constant wired to it and see if that helps?

[Arroyo]

Nope. I'm not using local variables.
Already using request memory deallocation without solving the problem.

[James.M]

Are you running the subVIs in parallel, causing the arrays to stack up memory at the same time? If you run the subVIs in series, then they should each allocate and release memory before/after the other subVIs run.

You said "just the main" VI's Front Panel is open. So why can't you make the subVIs inline to ignore that memory allocation required of displaying on the front panel?