D
dbeavon
Guest
>> I don't think Progress tech support wants to investigate PASOE memory leak That isn't totally accurate ... tech support was very helpful when I had a larger leak. And when I isolated the repro myself. But now that my _mproapsv processes only grow to about 4 or 5 GB in a week, they seem a bit less inclined to help investigate (...especially if I cannot independently pin-point the lines of ABL code in our environment that are responsible). Of course this is the extremely hard part when the memory leaks slowly over the course of an entire week. In the .Net world I can do lots of other things to find my own leaks - even gradual ones - like open up memory dumps on my own. It is frustrating that I don't have quite the same tools in ABL - especially since when the leak is typically in native code (msagent process host, and not my custom ABL).
Continue reading...
Continue reading...