L
Laura Stern
Guest
1. I don't know why you're saying that "if a procedure was persistently run from an ABL class, INSTANTIATING-PROCEDURE can no longer help". INSTANTIATING-PROCEDURE still gives a valid answer for a procedure run persistently. So I have a feeling I'm misunderstanding what you're saying. 2. We have another way to know the objects/procedures that are leaked and where they were created. It's called logging. What we are missing here is a program to read the sometimes lengthy log file to cull out which objects are still around (created but not deleted). It is not difficult to write this in the ABL. In fact, someone in tech support recently wrote such a program and we could probably post it somewhere. 3. You can also use the dynamic object tracking feature of the debugger , which is extremely effective if you have a limited scope of code that you think is causing a leak. 4. Knowing what program created an object is not necessarily tell you who should be deleting it. But I agree it helps to understand the context of what that proc/object is being used for. 5. We currently have no plans to expand the use of INSTANTIATING-PROCEDURE or something else like it, e.g., for classes.
Continue reading...
Continue reading...