control resizes and repositioning on runtime

[shrekt]

Dear All,

I am using LV2009 and Win7, also checked on XP.

I am resizing and repositioning  50-60 controls and indicators on run time.

This program runs perfeclly for 12-16 hrs, but it automatically resizes and repositions in runtime, and some of them disappears.

When in this condition, i debugged the code also, the value, size and position of the indicator is applied perfectly but cannot be seen on thefront panel.

i have to restart the application and then it runs perfecly for 12-16 hrs and problem occurs.

Any suggestions,

Shrek

[aeastet]

Does the program contrinue to run or does it stop functiong? (i.e. still open but not doing anything)?

[shrekt]

The program continue to run but only the numeric indicators goes haywire.

other modules of the program which is in parallel while loop runs perfectly.

does it have something to do with LV 2009 bug about the property nodes: 195627 or 179002

link: https://www.ni.com/en/support/documentation/bugs/10/archived--labview-2009-sp1-bug-fixes.html 

Regards,

Shrek

[aeastet]

Can you post your code?

[aeastet]

---

@shrekt wrote:

The program continue to run but only the numeric indicators goes haywire.

other modules of the program which is in parallel while loop runs perfectly.

does it have something to do with LV 2009 bug about the property nodes: 195627 or 179002

link: https://www.ni.com/en/support/documentation/bugs/10/archived--labview-2009-sp1-bug-fixes.html 

Regards,

Shrek

---

I would say that 179002 seems unlikely if LabVIEW is not crashing.

195627 could be more likely.

It sound to me like some sort of a memory leak. Especially since you can run for a time and then consistently shut down about the same time. I would look for references that are not being closed. Look for places where you are using memory and see if you are building arrays or things like that that could be using all of your memory. You are using up all of your memory or have a memory leak it sounds like.

Open the task manager and look at the memory used by your application then come back a few times to see if it is getting bigger. You can also look to see if the number of handles are getting bigger. This will tell you that something is being called over and over again but not being closed each time.

[shrekt]

Thank you for the reply,

i was constantly writing the property nodes, now for temp solution i designed the software in such a way that it will write when needed and it worked,

but i am doing testing now,

Regards,

Shrek