Reference Leak using cloneable module?

[gohawks12]

Hi, I have created an application that launches two clone modules for two power supplies.  When the program ends, I noticed that there were two Reference Leaks.  I took a screen shot of the results from Desktop Execution Trace Toolkit.  I am not sure what is happening.  I have attached screenshots for how I initialized the modules and how I stop them.  I have also attached the main.vi of my PSU module.

Anyone have an idea why these Reference Leaks were occur? Thank you

 

[ChrisFarmerWIS]

I see that you're passing the broadcast events from both instances of the PSU Start Module vi into separate User Event inputs on the DQMH_REG_EVENTS node.  You don't want to do that.  Just pass it from one of them.

[drjdpowell]

"Reference Leaks" in the DETT are references closed by LabVIEW when a VI stops.  Sometimes this is an actual leak, but sometimes this is a deliberate architectural design decision.  Don't know about details of DQMH, but you'll find a "leak" or two in the Actor Framework, for example.  So I wouldn't worry about two supposed leaks.  The thing to worry about is a growing leak, that keeps producing references until failure.