Hello,
Yes, I agree.
The problem was that not all instances of the class with the active object were being destroyed, which resulted as you said, in loops left in memory. In the development mode somehow this were taken care and I did not even noticed, as labview shutdown these loops. However, in executable mode, there will be an RESETING VIs problem if the active objects are not properly destroyed I realized this using the Desktop Execution Tracer tool kit by certifying myself that all instances of classes with active object were destroyed while in development mode. To my surprise, I exited without destroying some instances, and after I shut down everything properly the problem is gone forever!
thanks for your help