LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

array memory leak

Hi,


We've been having a memory leak on a VI that we intend to run for long periods of time. We've isolated the SubVI that is causing the problem (attached), but have not been able to eliminate the memory leak, even with the Request Deallocation VI. Any help here would be much appreciated.

0 Kudos
Message 1 of 3
(2,489 Views)

Hi adp,

 

wow, such a small vi with so many violations of style guide:smileyvery-happy: (Cleaned version attached)

 

Can you provide sample data (make them default value in the controls)? What kind of memory leak?

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 3
(2,460 Views)

We probably need more information.

 

  • How big ar the arrays?
  • Are the sizes always the same?
  • What is the subVI supposed to do?
  • Do you have some typical data and typical settings?
  • Why are the size controls I64?
  • Who wrote this VI? It seems to break any common coding guidelines (the LabVIEW 8.6 cleanup tool helps quite a bit to make sense of the diagram).
  • What observations led you to suspect a memory leak in this subVI?
  • Do you test with the front panel of the subVI open or closed?
  • ...

 

In any case, "request deallocation" is probably not a good idea. That would only make sense if you only call the subVI once and then go on to different tasks.

0 Kudos
Message 3 of 3
(2,459 Views)