D
dbeavon
Guest
I think I will open a support case because it is clear that there is a leak within the ms-agent process. One thing that we started doing is trimming inactive ABL sessions out of the agents every hour. My understanding is that this should absolve us of blame for leaks. Because memory that is outside the boundaries of CURRENT sessions is not reachable and not our responsibility if we can't manage it anymore. Does that sound right? Shouldn't Progress reclaimed all memory used by any individual ABl session that has been trimmed? Or are we responsible for making sure the ABL session memory is clean and spotless, before the session is trimmed. It seems unreasonable for an ABL programmer to be responsible for cleaning up everything, eg static members of classes, etc.
Continue reading...
Continue reading...