S
slacroixak
Guest
At last I ask around about this topic I've been wondering for ages I'd like to identify the ABL objects or procedures that have caused persistent procedures or objects leaks. A leakage is easy to spot with the SESSION:FIRST-PROCEDURE/FIRST-OBJECT and NEXT-SIBLING pattern. When dealing with a procedure that was run by another procedure, one can identify the caller procedure with hCalleeProc:INSTANTIATING-PROCEDURE:FILE-NAME if it is still running. However, if a procedure was persistently run from an ABL class, INSTANTIATING-PROCEDURE can no longer help. The same problem comes when you want to identify what procedure or class has launched an instance of a class. The Progress.lang.Object offers a NEXT-SIBLING and PREV-SIBLING property but it does not seem to provide an InstantiatingObject property yet, that would also be required by procedure object if it was launched from an ABL Object. At last, the INSTANTIATING-PROCEDURE attribute is also available for low level object types (dyn buffer, dyn temp-table, or GUI widgets). What if those are created by an ABL class? Did I miss something in the doc? Has Progress a plan to offer a facility to manage this kind of situation? Thanks /Sébastien
Continue reading...
Continue reading...