CPU usage and ram usage increases slowly while streaming with IMAQdx

[Asasafuchi]

Hello,

I am trying to acquire data with the NI-IMAQdx vi and everything works except that I noticed that the streaming slowly eats up more of the cpu and ram even while idling i.e. not storing or doing anything else than streaming. I tried streaming through NI-max and saw that the cpu and ram usage remains rather constant during streaming. Does anybody know what could be the potential cause for the increasing usage of my cpu and ram?

[Andrey_Dmitriev]

---

@Asasafuchi wrote:

Hello,

I am trying to acquire data with the NI-IMAQdx vi and everything works except that I noticed that the streaming slowly eats up more of the cpu and ram even while idling i.e. not storing or doing anything else than streaming. I tried streaming through NI-max and saw that the cpu and ram usage remains rather constant during streaming. Does anybody know what could be the potential cause for the increasing usage of my cpu and ram?

---

So , the very basic example like "Acquire most recent images" from examples "out of the box" also caused resources leakage?:

[Asasafuchi]

Hey, no this example does not cause resource leakage. I forgot to mention that I am running LV2015, and one thing I noticed is that the amount of handles slowly increases when running my code.

[Andrey_Dmitriev]

---

@Asasafuchi wrote:

Hey, no this example does not cause resource leakage. I forgot to mention that I am running LV2015, and one thing I noticed is that the amount of handles slowly increases when running my code.

---

Then obviously the problem is in surrounding code. Could be opened and not closed file, reference, may be queue, etc.

Sometimes the LabVIEW Desktop Execution Trace Toolkit is helpful for such kind of troubles.

[Asasafuchi]

Yes, the surrounding code definitely seems to be the problem. I have tried running the performance and memory tool and disabled the VIs that take consume the most memory/cpu usage but that didnt seem to be the problem. Do you have any tips on how I could possibly debug memory leaks in large code such as the one I have?