From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
09-04-2015 09:41 AM
Is this normal?
I have a source code that runs parallel loops to acquire counter measurements, analog inputs, digital pulse generation and some loops dedicated to calculations and display.
If I run my source code, the memory used by labVIEW slowly increasing. it is fluctuatiinf but there is an increasing trend.
If I run the execurable of the same program, the used memory fluctuates but stays about the same over time.
I hope someone has the "under the hood" inight to expolain what is happening here
I monitores the memory used in windows task manager.
09-04-2015 10:38 AM
Sounds like the debugger is storing data and creating a leak. Since the executable doesn't have this, no leak.
09-04-2015 10:55 AM
Maybe you do still have a leak, but with less memory requirements (because no IDE) it might take longer to become a problem. I'd run long term testing over a weekend or something with Performance Monitor (built in Windows program) logging various memory statistics.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
09-04-2015 11:39 AM
Thanks for the advice.
I'll let the executable running over the long weekend.
09-04-2015 12:25 PM
Thanks for your time. What you say makes sense.
What I don;'t understand is that, the VI analyser is dutifully warning me that a VIs has debugging enabled:
"This VI has debugging enabled, which can reduce performance slightly. Consider disabling debugging in the VI Properties >> Execution dialog box for this VI. "
On the other hand, going one by one to uncheck the enable debugginh flag for each VI is not efficient when i have 30 VIs.
Is there a way to turn this falg off for all VIs in the LV project or in an entire hierarchy?
09-04-2015 12:30 PM
With VI Server you can do this programatically. Open a reference to a VI based on the path, change this setting, then invoke the save. But honestly this setting eats up very little performance, and I wouldn't expect it to take up more as the VI runs, so I don't think this is your fix.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord