Editing front panel causes private memory to rise rapidly

[Probotector]

Hi all,

I'm working on a fairly small project including som librarys and classes. An unpleasant behavior has started to happen when I'm editing the main GUI front panel.

When I move objects around on the front panel or adds new controls/indicators to it the updates are really slow. I have also noticed that the private working memory (RAM) for LabVIEW increases dramatically with each small change. The working memory (RAM) piles up and finally it prevents me from saving my work due to insufficient memory. This behavior started recently and it is just when I edit my GUI VI.

The GUI front panel isn't too advanced, roughly it contains a couple of tab structures, some graphs, multi-column listboxes, buttons etc. No overlapping objects and so on..

Any ideas why this is suddenly happening?

/Jon

[Hooovahh]

• Include code whenever available.  Asking somebody to troubleshoot your software without any code is like asking your mechanic to fix your car without taking your car to him.

Source

That being said the only thing I could guess if you are copying existin controls controls, and they have lots of data stored in them.  Because copying the control, copies that data too.  You may want to clear the data in a graph before copying it for example.  Or if you have large arrays empty them first.

If you are making blank new controls no idea why this would happen.

[Probotector]

Yes, I fully agree that adding the code to your forum subject is the best way to go. Unfortunately in this case, a lot of the code is confidential and must not leave the premises.

What I'm hoping for is if there is some well known bug that could cause this memory behavior and if there is any possible workarounds to it.

And yes, it even happens when I add a new simple boolean button..

[Hooovahh]

Oh another thing worth mentioning (and mentioned in the guidelines linked earlier) is what version of LabVIEW and other tools are you using?  Not that I think it matters but this issue may not exist in newer versions of LabVIEW.