Memory issues

[1984]

Hi,

we recognized that an application we already handed over to our customer, consumes more and more memory all the way until the app stops with an error message.

I'm not saying at all that this is DQMH related but as the app uses fair amount of modules and it launches gazillion requests I post it to the DQMH forums as well. All the details are in this post: https://forums.ni.com/t5/LabVIEW/Application-eating-memory/td-p/4421167

Also while typing this, I've found a post on the DQMH forums suggesting that there is a memory leak in the framework. The post is here: https://forums.ni.com/t5/DQMH-Consortium-Toolkits/Memory-Leak-with-Private-Events/m-p/4376511#M2937

Any chance that it is related? We use the latest DQMH release.

Pls let me know if you have any ideas.

Thanks!

[Darren]

The only known memory leak in the framework is the one you linked to. If you have DQMH 7.0.1, and you have run the DQMH Validate Module tool on all your modules to have them all include 7.0.1 fixes, then I'm not aware of anything DQMH-related that would cause the leak.

One of the best tools for identifying memory leaks in terms of diagram constructs (Build Array, Concatenate String, etc.) is Profile Buffer Allocations (Tools > Profile > Profile Buffer Allocations), make sure you use that if you haven't already.

And of course, for identifying reference leaks, the Desktop Execution Trace Toolkit is the best tool.

[1984]

I'm pretty sure that I identified the dqmh module giving me headache. Its not related to the framework, the problem is in between the chair and the keyboard.

The problematic module read a gmail account in every 30s and most likely I forgot to close at least one reference so it increases the memory need by couple MBs in every 30s.

I will investigate it later, for now the module is disabled which is fine as it has nothing to do with the core functionality of the code.