L
Lieven De Foor
Guest
I feel this one is closely related to my forum post: Investigating memory leaks - ABL memory profiler community.progress.com/.../38976 For .NET/hybrid objects a .NET memory profiler can sometimes help, but for pure ABL objects that is not an option. Finding out what objects hold a reference to a leaking object should be query-able information, either from some run-time object property, or through logging, although the former seems more practical to build a retention graph.
Continue reading...
Continue reading...