Page History
...
Note that VLF-ONE has a similar checking facility, see Major Object Leakages Checked in Developer Mode.
A common resource utilization issue encountered in Windows applications is that when you close a window, not all of the resources associated with it are freed up for reuse. This is called 'resource leakage', and if left unchecked, it may eventually cause your application to fail or act unpredictably. To help you in this area the VLF includes a simple diagnostic tool to track some resource leakage at a high level.
...
This message is saying that a VL component (in this case, a command handler instance named DF_DET1) was not destroyed when the window was closed.
In other words, DF_DET1 has 'leaked' resources. You should investigate the cause of this and try to prevent it. If you can't work out why this message is being displayed, you should consult your Visual LANSA mentor for VL application design advice.
In VLF applications of simple to medium complexity, you are unlikely to see this message. However, as the sophistication of your VLF and VL application components increases, you may encounter this message.
...
The circular reference path may be even more complex. Component 'A' might refer to 'B', which refers to 'C', which refers to 'D', which refers back to 'A'. This is a much longer path, but it is still circular in nature.
...
- Try to avoid using Reference(*Dynamic) variables or object reference collections that are scoped across an entire BEGIN_COM/END_COM block (that is, across your whole VL program).
- When they are used, make sure that structured logic is in place (and used) to remove or nullify any object references that they may contain.
- When Scope(*Application) variables or collections are used to track object references, make sure that logic is in place (and used) to remove the references again at the appropriate time.
...