To understand why this message occurs see Why does this message appear?
You should initially check these things in your code:
- That your uInitialize and uTerminate methods symmetrically invoke the corresponding #Com_Ancestor.uInitialize and uTerminate methods.
- That your uTerminate logic empties all collections and lists.
- That your uTerminate logic sets all stored references to null.
- That your uTerminate logic asks any other object keeping a reference to the named object, to drop that reference.
Note: The existence of this VLF-ONE developer=YES object create/destroy tracking feature is absolutely no guarantee that your VLF-ONE application is not leaking resources in other ways that it cannot detect.