Not enough memory to complete this operation

[Jeon17]

It doesn't always take the same time to increase, but this time it took about 1 hr (quite faster than before). And I feel like something is stacked to the LabView.exe after this sharp increase. Even if I stopped running the LabView, the increased memory usage is maintained and the response gets really slow. 

[AeroSoul]

Does Labview remaing running in the background, after you supposedly exit it? Does it still show in the Task manager?

[Terry_ALE]

---

@AeroSoul wrote:

Does Labview remaing running in the background, after you supposedly exit it? Does it still show in the Task manager?

---

If there are unclosed library calls then those could remain in memory.

[Jeon17]

When I stop running, then it stops running and doesn't remain running in the background. But the increased memory usage (like 1,000,000K~) is maintained. And I exit Labview (doesn't show in the Task manager anymore) and reopen/re-run the program, the memory usage starts from 100,000K~.

[mcduff]

---

@Jeon17 wrote:

When I stop running, then it stops running and doesn't remain running in the background. But the increased memory usage (like 1,000,000K~) is maintained. And I exit Labview (doesn't show in the Task manager anymore) and reopen/re-run the program, the memory usage starts from 100,000K~.

---

My guess is a reference leak somewhere. It's hard to tell from your block diagram. Something like a new DAQ task continuously being made without the previous one being closed and cleared.

[JÞB]

 There is or used to be a nice Knowledge Base article on working with large data sets in LabVIEW. 

I'll try to find it but, it should be in my tag cloud.  (Used to be in my macros)

Nothing posted in an inline png explains 2Gb+ although you could avoid some data copies, are abusing local variables and have some probable race conditions.   A refactoring is warranted!  Call for a consultation if, your boss can afford me.

Heck, I'd give a cut rate to an academic institution. 

[thols]

---

@JÞB wrote:

 There is or used to be a nice Knowledge Base article on working with large data sets in LabVIEW. 

I'll try to find it but, it should be in my tag cloud.  (Used to be in my macros)

Nothing posted in an inline png explains 2Gb+ although you could avoid some data copies, are abusing local variables and have some probable race conditions.   A refactoring is warranted!  Call for a consultation if, your boss can afford me.

Heck, I'd give a cut rate to an academic institution. 

---

Is this the one, JÞB?

If it is a reference leak and you cant find it, DETT can help you to find it. But if the design is bad and there are race conditions, that might not help you, so you may need to refactor anyway just to be certain that there is no reference leak.

[AeroSoul]

---

@mcduff wrote:

---

---

My guess is a reference leak somewhere. It's hard to tell from your block diagram. Something like a new DAQ task continuously being made without the previous one being closed and cleared.

---

Would a reference leak persist even with Labview closed?

[mcduff]

---

@AeroSoul wrote:

---

@mcduff wrote:

---

---

My guess is a reference leak somewhere. It's hard to tell from your block diagram. Something like a new DAQ task continuously being made without the previous one being closed and cleared.

---

Would a reference leak persist even with Labview closed?

---

From the OP:

"When I stop running, then it stops running and doesn't remain running in the background. But the increased memory usage (like 1,000,000K~) is maintained. And I exit Labview (doesn't show in the Task manager anymore) and reopen/re-run the program, the memory usage starts from 100,000K~."

From the OP's comment, once LabVIEW is exited the memory is no longer allocated. When the OP just stops the LabVIEW program the memory is still allocated because LabVIEW is still running, just not the OP's program.

[Jeon17]

Yes, that's correct! And I'm trying to modify the code, but still running the original program. During running, I found a new situation where the memory usage is changed when I change the front panel tab. On my main program front panel, it has several tabs to control the program. The figure below is the main tab on the front panel to monitor temperature mostly shown on the screen. When this tab is shown on the screen, the memory usage sharply increases at some point up to 2,500,00K~. And when I click another tab, the memory usage decreased to ~1,500,000K. It's still high, but I found this situation several times. Unfortunately, 1,500,000K memory usage is maintained. I tried to clear the chart on the main tab but it didn't show any difference.