G
Garry Hall
Guest
I have not used pmap, and don't know much about it. I would guess this particular region is the heap. Your stack memory would possibly grow if you caused something deeply nested in the AVM (deeply nested functions/methods maybe). The heap is intentionally dynamic, and on linux/unix it doesn't go down. But that is probably a long way abstracted from your investigation. You'd want to know what particular ABL constructs are consuming this memory (most things are in the heap). There are a number of things you could do to investigate. bob.p is a favourite (I think you'll find it in the kbase) to track down leaked dynamic objects. That is where I would start. Tech Support can assist with this investigation.
Continue reading...
Continue reading...