01-15-2025 04:56 AM
Hey guys.
I'm trying to open a reference to all the vi's of a packed labrary, I didn't bother to run the vi's after I opened the reference, I just closed the reference, but I noticed that my memory wasn't freed up, I think it might be because I'm not freeing up the packed library, but I can't find out where I can free it up or maybe it's because of something else that prevents me from freeing up the memory.
Run Result
"Main"
"Load VI From Lvlibp"
The Get Memory Usage VI is called "kernel32.dll/GlobalMemoryStatusEx" library to get free memory.
01-15-2025 05:15 AM
It depends, how memory manager implemented internally and which value returned from this function.
Try to use VMMap from SysInternals instead to get more accurate and detailed footprint of the memory.
01-15-2025 06:34 AM
LV likes to hold on to memory in case it needs it again, don't worry about it.
01-15-2025 05:18 PM
01-15-2025 07:42 PM
Thank for your advice.
I will use it to monitor my memory status.
01-15-2025 07:45 PM
Thanks for your response.
I would like to prioritize freeing up the original space before my new memory usage, because LabVIEW consistently fills up my application with memory, which I think can be and its something that affects the user experience.
MapleBay
01-15-2025 07:54 PM
Thanks,I using "Get Memory Status" to be my memory monitor. But I can't to get the same result.
And when I close my VI or project, LabVIEW still won't free my memory until I close LabVIEW!
MapleBay