F
Frank Meulblok
Guest
Well, in the previous thread you didn't mention you were using OO code 
Class instances behave a lot like persistent procedures when it comes to this: They stick around until deleted, and so do any static temp-tables they define. Main difference is that classes can get garbage collected as well as being explicitly deleted, and starting with 10.2B they can get cached for faster re-use instead of being completely removed. The class caching can be ruled out by starting the appserver agent with -reusableObjects 0 startup parameter. The article How to detect ABL Memory Leaks with Dynamic Objects Logging Julian already referred to in the previous thread can also be used to detect leaking classes, assuming the DynObjects.Class subtype is being logged.
Continue reading...
Class instances behave a lot like persistent procedures when it comes to this: They stick around until deleted, and so do any static temp-tables they define. Main difference is that classes can get garbage collected as well as being explicitly deleted, and starting with 10.2B they can get cached for faster re-use instead of being completely removed. The class caching can be ruled out by starting the appserver agent with -reusableObjects 0 startup parameter. The article How to detect ABL Memory Leaks with Dynamic Objects Logging Julian already referred to in the previous thread can also be used to detect leaking classes, assuming the DynObjects.Class subtype is being logged.Continue reading...