@Sajeesh wrote:
hi
the programe is a bit large,Through Desktop execution trace toolkit it was found so many memory resize,allocations etc.
a part of code is attached
Hi Sajeesh,
The code you attached doesn't have any calls to DQMH. We have done multiple applications with cloneable DQMH modules and by themselves, they do not have a memory leak. Seems like the code added to the cloneable modules is causing the issues.
Without knowing much about your application, a couple of suggestions I have that have helped us make DQMH modules more performant:
- If you are doing memory-intensive operations, keep the DQMH module headless, meaning no GUI for the module. This will avoid having your module swap between the UI thread and other threads. If you are currently displaying things on the module, consider instead sending them to another module. One module does your display, the other module does the data manipulation.
- If you are sending large pieces of data in between modules, wrap them in a DVR and send the DVR instead.
If you post the attached code in the generic LabVIEW forums, others can help you make it more performant.
I hope this helps.
Best regards,
Fab
