LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to leave allocating new memory for operation openinig and closing subvi dynamically

Please anybody help me I'll try experimentally understand it but always new memory allocating with every dynamically call of subvi - approximately 4..8 KB every time and subvi is consists only loop.

0 Kudos
Message 1 of 11
(2,289 Views)

Step 1: Calm down.

Step 2: Please write in complete sentences, not one run-on sentence.

Step 3: Please explain your problem more clearly. I have no idea what your specific issue is, and I can't really understand what you're trying to say. I don't know if you're referring to a memory leak, or to a behavior you didn't know would happen, but is supposed to happen. If possible, please post code so others can try to replicate the condition.

0 Kudos
Message 2 of 11
(2,284 Views)

Thank you very much for your answer, please see below in LV9

 

Constantly grow with almost every call - most likely good applications should be much  8-)

 

I'm very dreaming to do application for 24/7 mode

0 Kudos
Message 3 of 11
(2,280 Views)

-Deleted-

0 Kudos
Message 4 of 11
(2,277 Views)

Where are Knights of NI - they have save me, how to do that memory is no grow on every call

0 Kudos
Message 5 of 11
(2,253 Views)

I do not see any memory leak when I run your project, in both LabVIEW 2009 and LabVIEW 2011.  Memory usage according to the task manager stays constant regardless of how many times I show or hide the subVI.  By the way, in the subVI, there is no need to open the VI reference.  You can remove the open and close reference; if you use a property or method node of the VI class and don't wire the refnum input, it will implicitly reference the current VI.

0 Kudos
Message 6 of 11
(2,242 Views)

Thank you very much Nathand nevertheless I saw how grow value in task manager.

0 Kudos
Message 7 of 11
(2,236 Views)

Thank you very much Nathand nevertheless I saw how grow value in task manager. I've checked it on exe file

0 Kudos
Message 8 of 11
(2,236 Views)

Are you saying the increase in memory happens only when it's running as an exe? Do you see it if it's running within the LabVIEW development environment?

 

Aside: You should not hard-code paths in the code.

0 Kudos
Message 9 of 11
(2,233 Views)

Once more I've checked it (I tested always in exe file) and what I saw in Task manager - at once 32248 KB after 100 times I clicked mouse - 32972 KB, well what does it mean I don't know - may be for me first of all - calm down.

0 Kudos
Message 10 of 11
(2,232 Views)